Use env vars in Docker compose and swarm mode #20
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
Member
a-earthperson
commented
Feb 22, 2025
a-earthperson
commented
- deployment seems stable
- reverting to fewer containers for review branches
- add placement constraints
- update CODEOWNERS
- app is buildable (a) locally, (b) using docker-compose, and (c) with docker-swarm.
- split .env into local, compose, and stack
- add support for multiple brokers in swarm mode
- persist rabbitmq data in compose mode
- add secrets and configs in compose mode
- update CD steps to expose and scale brokers, workers using Space UI
- fix a bug where NumWorkers was force-set to 1.
- increase healthcheck start interval to 5min for very slow hosts in swarm mode
- remove unusable test, include a stub test
- include a deployment config for swarm mode
- expose env vars to stack, compose, and local dev environment
- update CD pipeline to use new configs
- add health-checks in compose
- cleanup stack file
- remove unused env vars
- expose RMQ runtime params as env vars
- read and use env vars as config, with fallback
- refactor microservices to not use hardcoded paths
- remove unneed files
- gracefully handle exposing and using JWT secrets as env vars or secret file
- added a stress test file for the microservice.
`docker compose -f docker-compose.yml up -d` in the project root directory. - Added a stress test file for the microservice. - Added log message support for quantification producer and consumer. - Removed storage queue from the quantification workflow. Workers can send the output directly to the database now. - Added prefetch limit for both quantification (32) and executable (1). - Converted the queuing method to sync from async. - Increased the request body limit to 50 mb for the microservice. - Quantification consumer will be compiled inside the /dist/packages/microservice/job-broker-consumer folder instead of the /dist/packages/microservice/job-broker/consumer folder.
…send requests to the `v2-app` that has already been deployed instead of `localhost`.
`docker compose -f docker-compose.yml up -d` in the project root directory. - Added a stress test file for the microservice. - Added log message support for quantification producer and consumer. - Removed storage queue from the quantification workflow. Workers can send the output directly to the database now. - Added prefetch limit for both quantification (32) and executable (1). - Converted the queuing method to sync from async. - Increased the request body limit to 50 mb for the microservice. - Quantification consumer will be compiled inside the /dist/packages/microservice/job-broker-consumer folder instead of the /dist/packages/microservice/job-broker/consumer folder.
…send requests to the `v2-app` that has already been deployed instead of `localhost`.
- read and use env vars as config, with fallback - refactor microservices to not use hardcoded paths - remove unneed files
- update CD pipeline to use new configs - add health-checks in compose - cleanup stack file - remove unused env vars
- add support for multiple brokers in swarm mode - persist rabbitmq data in compose mode - add secrets and configs in compose mode - update CD steps to expose and scale brokers, workers using Space UI - fix a bug where NumWorkers was force-set to 1.
- reverting to fewer containers for review branches
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.