Tweaked to allow multiple parallel instances#2
Open
MBybee wants to merge 4 commits intowebysther:mainfrom
Open
Tweaked to allow multiple parallel instances#2MBybee wants to merge 4 commits intowebysther:mainfrom
MBybee wants to merge 4 commits intowebysther:mainfrom
Conversation
Adjusted the .env and docker compose files to allow for customization to make it easy to run multiple parallel instances with different project names, orgs, settings, and dbs. Added a .env_1 to show an example of this customization. This was tested a fair bit (currently in use with a 3 system landscape on one docker host right now). No changes should be required to the docker compose, just clone off multiple copies of the repo directory, adjust the .env file details, and run "docker compose up -d" to deploy, or "docker compose down -v" to destroy.
Decided to have a few less defaults, they're just a bit messy and it felt a little inconsistent.
Owner
|
Thanks for the contribution, just a few changes:
|
Author
|
Will do! |
Switching from ${PROJECT_NAME} to ${COMPOSE_PROJECT_NAME}
Removed old file
Author
|
Ok, made that change to the .yml and .env, plus the rename. Not used to the fork PR workflow, but I think it's updated. Hopefully I understood your feedback properly! |
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
2 participants
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.
Adjusted the .env and docker compose files to allow for customization to make it easy to run multiple parallel instances with different project names, orgs, settings, and dbs. Added a .env_1 to show an example of this customization.
This was tested a fair bit (currently in use with a 3 system landscape on one docker host right now). No changes should be required to the docker compose, just duplicate the core repo directory, adjust the .env file details, and run "docker compose up -d" to deploy, or "docker compose down -v" to destroy.
It does make it slightly less 'minimal', but hopefully only somewhat.
Hope this is useful! Your fork of Supabase was a massive improvement over the core, and far more efficient in practice.
Thanks so much.