makeitcount / makeitcount/saas-express-starter-kit
Support for SAAS variations
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
5. SAAS variations when it comes to how you handle the client DB.. single DB with tenant-id column? Separate DBs for each client? Or postgres with schemas? Separate DBs on separate instances? - all configurable.
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. Start by mapping how the starter kit currently handles the client database, then compare the requested single database with tenant IDs, per-client databases, PostgreSQL schemas, and separate instances. Done means the supported configuration scope and acceptance criteria are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript, node.js, postgresql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100