Edit history

Earlier versions of Add PostgreSQL support as an alternative to SQLite in refactor, newest first.

Current version | Edited by Rex
Changes
SQLite is a great default for simple single-server setups. PostgreSQL would complement it well for users running Fluxer on existing infrastructure with shared database services, and handles concurrent access better at scale.Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Add PostgreSQL support as an alternative to SQLite in refactor

Problem

SQLite can be unreliable when the database file is stored on network-attached storage, which is a common pattern in containerized/Docker deployments. This could lead to data corruption for self-hosters who don't store their data on a local filesystem.

Proposed solution

Support PostgreSQL as an alternative database backend alongside SQLite, configurable via an environment variable or config file.

Notes (optional)

SQLite is a great default for simple single-server setups. PostgreSQL would complement it well for users running Fluxer on existing infrastructure with shared database services, and handles concurrent access better at scale.
Original by Rex
Show

Add PostgreSQL support as an alternative to SQLite in refactor

Problem

SQLite can be unreliable when the database file is stored on network-attached storage, which is a common pattern in containerized/Docker deployments. This could lead to data corruption for self-hosters who don't store their data on a local filesystem.

Proposed solution

Support PostgreSQL as an alternative database backend alongside SQLite, configurable via an environment variable or config file.

Notes (optional)

SQLite is a great default for simple single-server setups. PostgreSQL would complement it well for users running Fluxer on existing infrastructure with shared database services, and handles concurrent access better at scale.

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.