mirror of
https://github.com/BretFisher/jekyll-serve.git
synced 2026-07-22 13:53:45 -04:00
Why docker-compose and docker run ( help ) #23
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Vctrsnts on GitHub (Jan 7, 2022).
Hello.
I am trying to use its container, but I have a couple of doubts when it comes to using it.
Why put the "docker-compose" if the next thing you do is a "docker-run" (that's what I see if I check the entrypoint.sh)
What is the difference between jekyll and jekyll-server? because in your documentation I don't see any difference.
In its details, you explain "it will mount your current path into the containers / site, bundle install before running jekyll serve to, serve it at http: // : 4000". But my question is how are you going to "bundle" the container if it doesn't work until you do a "docker run" (all this using the docker-compose).
Thanks if you can help me
@BretFisher commented on GitHub (Jan 11, 2022):
docker runordocker-compose upboth work, so it's up to youjekyll-servestarts a server to run an existing site.jekyllimage can be used to create a site, or run other jekyll commands when you don't want to run the server by default. The are both mostly the same. You can see in the Dockerfile that alljekyll-servedoes is add a entrypoint script and change the CMD.jekyll-serveimage, it has a entrypoint script that will run bundle before the server starts.