Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the configuration for Read-only DB replicas #1671

Open
ballPointPenguin opened this issue Apr 9, 2023 · 0 comments
Open

Clarify the configuration for Read-only DB replicas #1671

ballPointPenguin opened this issue Apr 9, 2023 · 0 comments
Labels
🧹 chore 🧩 config .env and other configuration concerns

Comments

@ballPointPenguin
Copy link
Contributor

Problem:
Previously there was an optional var DATABASE_FOR_READS_NAME that served as a pointer to another value which could be managed programmatically to point to one of potentially many read-only databases.
In the great configuration refactor, this was replaced with a simple READ_ONLY_DATABASE_URL var which is more limited and must be explicitly set just once.

Suggested solution:
We need to decide if and how to support multiple read replicas in a way that works in Heroku and non-Heroku environments.

Alternative suggestions:
TBD

Additional context:
This came up during review of another PR #1663

@ballPointPenguin ballPointPenguin added feature-request For new feature suggestions 🧹 chore 🧩 config .env and other configuration concerns and removed feature-request For new feature suggestions labels Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧹 chore 🧩 config .env and other configuration concerns
Projects
None yet
Development

No branches or pull requests

1 participant