Why
CLAUDE.md currently rules out Postgres/MySQL/Redis without discussion — SQLite-via-Drizzle was chosen specifically so a self-hoster can back up the entire app by copying one file. The research suggested Postgres as an option for "larger deployments," but it's unclear that a household chore chart ever hits a scale where SQLite is the bottleneck.
This needs a decision, not an implementation, first
- Is there an actual scale/use case for Hestia that SQLite can't handle (multi-household SaaS-style hosting? Very large households?), or is this solving a problem Hestia doesn't have?
- Supporting two databases means maintaining two migration paths and dialect differences in Drizzle queries indefinitely — real ongoing cost for a project this size
- If there's no concrete driver, recommend closing this rather than scheduling it
Depends on
None.
Acceptance criteria
Why
CLAUDE.md currently rules out Postgres/MySQL/Redis without discussion — SQLite-via-Drizzle was chosen specifically so a self-hoster can back up the entire app by copying one file. The research suggested Postgres as an option for "larger deployments," but it's unclear that a household chore chart ever hits a scale where SQLite is the bottleneck.
This needs a decision, not an implementation, first
Depends on
None.
Acceptance criteria