-
Notifications
You must be signed in to change notification settings - Fork 94
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
[Feature] - Use postgres as database #476
Comments
Why is this a crucial feature when using kubernetes? SQLite should work without problems with as little data as wizarr saves. |
Cuz then I don't really need to have a persistent volume, I can just edit the config directly on my gitops solution and use Postgres as database. |
There are some things that cannot be saved in the database, such as uploaded files. They need to be saved on a persistent volume. |
That would be the case for people who actually use this feature. But then again they could make a persistent volume for that folder only, and also if we want to go a step further there are ways to save files in databases. Just need to enconde/decode it. |
SQLite is known to have file locking issues for network shares like NFS - not likely a huge problem for this service, since I assume the writes are pretty low-volume (so you are unlikely to have any collision issues where two writes are trying to happen quickly enough that the DB is locked), but it's possible. This is also solved by using non-NFS persistentVolumes like Longhorn (iSCSI), etc. I personally would love to see it since most of the *arr stack is now supporting Postgres, and Jellyfin itself is almost migrated to EFCore which will (in theory) unblock non-SQLite DBs via ORM. |
I'd like to see wizarr have an option to use postgres as its database. For users using kubernetes this is a crucial feature.
The text was updated successfully, but these errors were encountered: