riverqueue / riverqueue/riverui
multi-tenancy & nonstandard schema
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 236
- Forks
- 39
- Avg merge
- 3h 40m
- Merged PRs (30d)
- 23
Description
would you be open to MR which supported multi-tenancy?
we have 20+ tenants per environment, and it would be really nice to just connect to all databases in one ui, and then switch between them within the app, instead of host 20 instances of the ui
i imagine something like you say #3 here would work best
{
"prod": "postgres://.../prod?search_path=river0",
"staging": "postgres://.../staging?search_path=river0"
}
with the name being encoded into the url. the schema should be declared as a search parameter in that url, so nothing special needs to be done i think for schema.
currently riverui doesn't even work for us since we use a non-standard schema. (although maybe i am using the wrong parameter to set it?)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Review the linked discussion in issue #3, then inspect how connection URLs and schema parameters are currently handled. Done should include a way to configure multiple named databases, switch between them in the UI, and support the non-standard schema described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, typescript
- Domain
- databases, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100