Seperate docker compose file in staging and production for backup #850
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
docker/docker-compose-production.yml
Outdated
There was a problem hiding this comment.
I dont know how that file become empty .I updated it again
| @@ -18,7 +18,7 @@ jobs: | |||
| - uses: actions/checkout@v2 | |||
| - name: Start dependancies | |||
| working-directory: ./docker | |||
| run: docker compose up -d | |||
| run: docker compose -f docker-compose-staging.yml up -d | |||
There was a problem hiding this comment.
does this needs to happen only for staging?
There was a problem hiding this comment.
@shimilgithub Actually do we need this built-n-test in staging and production ?
Since we have both compose file now ,inorder to run the built-n-test ,we need to specify one thats why I added staging here .I think this file is using at the stage of local to github .
There was a problem hiding this comment.
As per this , during release also staging docker compose will run
| run: docker compose -f docker-compose-staging.yml run vachan-api-test |
shimilgithub
approved these changes
Jul 19, 2024
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.
Utilize newly allocated space in production(backup) #836
Separate Docker Compose files for staging and production. In the staging Docker Compose file, there is no Ofelia scheduler container, while in the production Docker Compose file, the Ofelia scheduler is included for backup