389 split instances #399
Merged
389 split instances #399
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
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.
Resolves #389
Also modifies build.yml to correctly deploy to the now separate instances for staging and production.
The new instance required newer versions of docker compose; hence the switch from
docker-composewhich is v1 todocker composewhich is current. Modified the old instance to use the new calls as well.once again, PRODUCTION HAS NOT BEEN TESTED UNTIL THE NEXT RELEASE. Proceed with caution.
Steps to reproduce:
tested to work successfully in the new staging instance