Added opt-in ghost service to docker compose
#21938
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cmraible
changed the title
cmraible
force-pushed
the
chris-eng-1957-add-ghost-service-to-base-docker-compose-setup
branch
from
75638de to
2cf9470
Compare
…ker-compose-setup
cmraible
changed the title
ghost service to docker compose
cmraible
deleted the
chris-eng-1957-add-ghost-service-to-base-docker-compose-setup
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref https://linear.app/ghost/issue/ENG-1957/add-ghost-service-to-base-docker-compose-setup
compose.ymlfile only runs Ghost's supporting services, and it's expected that you'll run Ghost locally on your host machine. This commit adds aghostservice to ourcompose.ymlfile, so you can optionally run Ghost itself in a container using docker compose.ghostservice is opt-in using docker compose profiles, to maintain the current behavior of only running supporting services as the default.WORKDIRarg, which is used to optionally specify an alternative working directory, is not propagated from one build stage to the next, so it has to be manually added as anARGin each stage. This was necessary to use the same Dockerfile for devcontainers (which require the WORKDIR to be/workspaces/ghost) and docker compose, where we use/home/ghostin alignment with the production image.