Use docker-compose profiles + cleanup old volume-mount cludges #4936
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.
Refactor to remove some no longer needed deploy steps now that we no longer mount the repo.
Technical
up
commands needed for each searverdown
before weup
! Docker should automatically detect that oldev:latest has changed, and restart the right things.make i18n
since the built i18n files are in the image.profile
is not specified for a service, that service is always started! Don't want that. Added a test to make sure no one accidentally does this.Testing
profiles: ["foo"]
to web in docker-compose.yml, andprofiles: []
to all other services (also in override)docker-compose --profile foo up -d --no-deps
only starts webscale
profiles: ["foo"]
to web & solr in docker-compose.yml, andprofiles: []
to all other services (also in override)docker-compose --profile foo up -d --no-deps --scale web=2
starts 2 web nodes, one solr nodeScreenshot
Stakeholders
@cclauss