You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When following the instructions in the README to run the Quarkus.io website using Docker Compose, I experienced a noticeable delay during the startup process. This happened both on my Windows 11 system and within a WSL instance. The terminal displayed repetitive logs and warnings, which made it unclear whether the process was progressing or stuck.
It wasn’t until several minutes later that the site started successfully, and I saw the expected output indicating the server was running. As someone new to Jekyll, I was unsure how long the process should take and initially assumed there was an issue with my setup.
I suspect that other contributors, especially those unfamiliar with Jekyll, may encounter similar confusion when running the Docker Compose command for the first time. They might not know that the startup process can take a few minutes or what the expected terminal output should look like when the server is running.
Suggested Improvement
I recommend updating the README to mention the potential startup time for the site and include a note about the expected output once the server is ready. This would help set expectations for new contributors and reduce confusion during the process.
The text was updated successfully, but these errors were encountered:
josephaw1022
changed the title
Clarify Startup Time for Quarkus.io Website in README
Clarify Startup Time / Expected Terminal Output for Quarkus.io Website in README
Nov 29, 2024
Description
When following the instructions in the README to run the Quarkus.io website using Docker Compose, I experienced a noticeable delay during the startup process. This happened both on my Windows 11 system and within a WSL instance. The terminal displayed repetitive logs and warnings, which made it unclear whether the process was progressing or stuck.
It wasn’t until several minutes later that the site started successfully, and I saw the expected output indicating the server was running. As someone new to Jekyll, I was unsure how long the process should take and initially assumed there was an issue with my setup.
I suspect that other contributors, especially those unfamiliar with Jekyll, may encounter similar confusion when running the Docker Compose command for the first time. They might not know that the startup process can take a few minutes or what the expected terminal output should look like when the server is running.
Suggested Improvement
I recommend updating the README to mention the potential startup time for the site and include a note about the expected output once the server is ready. This would help set expectations for new contributors and reduce confusion during the process.
The text was updated successfully, but these errors were encountered: