Share common docker-compose.yml configurations (PROD and DEV enviroments)#79
Open
Share common docker-compose.yml configurations (PROD and DEV enviroments)#79
docker-compose.yml configurations (PROD and DEV enviroments)#79Conversation
- remove `docker-compose-consumer.yml` - add `G3WSUITE_RUN_HUEY` enviroment variable within `.env.example` (batch processing) - add `g3w-suite-consumer` within `docker-compose.yml` - refactor `docker-compose-consumer-dev.yml` in order to extend the base `docker-compose.yml` - remove `scripts/docker-entrypoint-dev.sh` - add support for `gunicorn.conf.py` within `scripts/docker-entrypoint.sh` (in order to share same server in various enviroments: PROD / DEV) - refactor `scripts/docker-consumer-entrypoint.sh` (ref. `G3WSUITE_RUN_HUEY`) - update `README.md` instructions related to batch processing usage - update `docker-compose.yml` version from `v3` to `v3.4`
docker-compose.yml configurations (PROD / DEV)docker-compose.yml configurations (PROD and DEV enviroments)
Raruto
commented
Sep 27, 2022
Raruto
commented
Sep 27, 2022
| - FRONTEND | ||
| - G3WSUITE_GUNICORN_MAX_REQUESTS | ||
| - G3WSUITE_GUNICORN_NUM_WORKERS | ||
| - G3WSUITE_GUNICORN_TIMEOUT |
Member
Author
There was a problem hiding this comment.
Check if the huey service requires setting a different / greater value for the timeout (ref: G3WSUITE_GUNICORN_TIMEOUT).
Raruto
commented
Sep 27, 2022
…ose.yml` Related to: #75 (comment)
Raruto
commented
Nov 7, 2022
Raruto
commented
Nov 7, 2022
1 task
Raruto
added a commit
to g3w-suite/g3w-client
that referenced
this pull request
Feb 7, 2023
…ProjectsRegistry~createProject(projectConfig)` Start addressing: #67 As a result of: #150 we intend to bring the development environment ever closer to the production one. Related to: #89, #292 and g3w-suite/g3w-suite-docker#79
…w-suite-docker into single-compose-file
Member
Author
|
@wlorenzetti To test the changes of this PR, add the following to your SCRIPTS_VOLUME=./scripts:/scripts # TEMPORARY: just to preview PR #79 (before merge)And then run: make reload ENV=prod
# 👉 same as: docker compose up -d |
1 task
This file contains hidden or 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
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.
List of changes:
docker-compose-consumer.yml(replaced by:docker-compose.yml)docker-compose-consumer-dev.yml(replaced by:docker-compose.yml)scripts/docker-consumer-entrypoint.sh(replaced by:docker-entrypoint.sh)scripts/docker-consumer-dev.sh(replaced by:docker-entrypoint.sh)make help(list available commands).env.example(G3WSUITE_RUN_HUEY) in order to enable batch processingdocker-compose.yml(g3w-suite-consumer)docker-compose.yml(dev-server)scripts/docker-entrypoint.shin order to supportgunicorn.conf.pyconfiguration file (PROD and DEV server)README.mdinstructions related to "batch processing" and "development" usageHow to test
To test the changes from this PR, add the following to your
.envfile:And then run:
make reload ENV=prod # 👉 same as: docker compose up -dIf tou want to test
debugpyintegration (eg. to inspect batch processing), update your.envfile:Reload containers:
make reload ENV=prod # 👉 same as: docker compose up -dGo to your local "g3w-admin" repository and attach the debugger:
Closes: #66
Closes: #150