-
-
Notifications
You must be signed in to change notification settings - Fork 271
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 Request] Add support for external database connections #186
Comments
+1 to this, and it's pretty important for my usecase. With kubernetes becoming less and less niche for those running servers at home, something with better support of the features necessary to run fully HA is highly desirable. Additional, and from the performance angle this time, between movies, tv, and audio, I'm at nearly ~75k items: root@<mahServer>:/mnt/user/media# find music -type f | wc -l
38802
root@<mahServer>:/mnt/user/media# find movies/ -type f | wc -l
2475
root@<mahServer>:/mnt/user/media# find tv_shows/ -type f | wc -l
31867 I've tuned the individual media management's SQLite DB's to the limited extent possible and that's helped them in the past (20k-ish items), but am once again starting to see slight sluggishness creep back in again. While Jellyseerr has far less transactional history to handle (e.g. no activity log for trying the same media object 60 different times, so far less history to parse), between them I feel hitting some boundaries are inevitable. Fan-friggin-tastic work on JellySeerr! I'm opening up a feature request here shortly to ask for a donation link - need some kind of way to support y'all! |
I made a duplicate on Overseerr, most likely if this is going to happen it should be made upstream, since Jellyseerr is a fork. [Feature Request] Add support for external database connections #3176 |
The main reason for asking here is that it's been requested several times already there, and appears (at least based on the amount of activity on them) that there's possibly little appetite for it. There's this discussion dating back to 2020, where I'd actually asked if the PO would be open to letting us 'directly fund / pay for' the feature, though no feedback up to now. They may be super busy, or maybe they just don't feel it fits with their vision for the application, but either way, it's at least been brought up. There's also this pr where someone has attempted to at least get the ball rolling. Given this fork's goals have been aimed at broadening the scope of the base overseerr project, perhaps they'll pick up the mantle. I understand it's potentially quite the undertaking, but my hope is that, given this note back in 2020 stating that it was technically already possible at that point and just hasn't been exposed, it may not be too big of a lift to bring it in over here. Keeping my fingers crossed regardless! |
…ed ssl for postgres config Fallenbagel#186
Is there any update for this? It is a dealbreaker for K8s users |
* chore(release): 1.4.0 * chore(release): 1.4.1 * chore(release): 1.5.0 * chore(release): 1.6.0 * chore(release): 1.7.0 * feat: support for postgresql * test(pgsql): disable root certificate verification * test(ci): temporarily change CI for local repo * fix: don't use SQLite idiom when using PgSQL * feat(db): add flag to toggle TLS for Postgres * feat(postgres and migrations): added migrations for postgres & imporved ssl for postgres config #186 * fix: restored workflow actions * fix: access order * fix: added pushover sound migration tto initial migration * fix: added option to log queries * fix: issue with session migration * chore: relocate pushover sound migration * feat: added logging option to other datasources * chore: small tweaks for the datasource. Added docs for db setup * chore: cleanup logs * fix: added default dates to postgres migration * fix: removed psql specific relation checks * chore: added some debug sanity checks * chore: added some more debug sanity checks * chore: added some more additional debug sanity checks * chore: added some more+ additional debug sanity checks * chore: mild log cleanup * chore: more log cleanup * chore: finish log cleanup * fix: added not null to migration so typeorm doesn't delete ids * chore: cleanup extra psql code * fix: remove eager load * docs: added documentation for migration to postgres * docs: added database option to bug template * feat: created docker-compose postgres file * fix: updated ts schema to align with change to migration * fix: switch timestamp to include timezone * fix: fixed indentation in psql docker-compose * fix: changed version to 0.1.0 to remove ui notification * style: fixed prettier in docker-compose.pastgres.yaml * chore: restored CHANGELOG.md * chore: revverted ts commit * fix: update pnpm lock with pg package * chore(pnpm-lock.yaml): updated pnpm-lock * docs: update docs to add psql set up info * refactor: clean up code from cr comments * feat: migrate blacklist * fix: fix issue with cypress tests * docs: update psql docs * fix: fix psql issue in user page; fix tiny psql error when selecting by empty list * fix: incorrect current date function * fix: null contraint with mediaAddedAt; fix psql col type * refactor: removed unnecessary import * feat: add postgres migration for streaming region --------- Co-authored-by: Fallenbagel <[email protected]> Co-authored-by: semantic-release-bot <[email protected]> Co-authored-by: zackhow <[email protected]> Co-authored-by: Ryan Algar <[email protected]> Co-authored-by: Ryan Algar <[email protected]>
* chore(release): 1.4.0 * chore(release): 1.4.1 * chore(release): 1.5.0 * chore(release): 1.6.0 * chore(release): 1.7.0 * feat: support for postgresql * test(pgsql): disable root certificate verification * test(ci): temporarily change CI for local repo * fix: don't use SQLite idiom when using PgSQL * feat(db): add flag to toggle TLS for Postgres * feat(postgres and migrations): added migrations for postgres & imporved ssl for postgres config Fallenbagel#186 * fix: restored workflow actions * fix: access order * fix: added pushover sound migration tto initial migration * fix: added option to log queries * fix: issue with session migration * chore: relocate pushover sound migration * feat: added logging option to other datasources * chore: small tweaks for the datasource. Added docs for db setup * chore: cleanup logs * fix: added default dates to postgres migration * fix: removed psql specific relation checks * chore: added some debug sanity checks * chore: added some more debug sanity checks * chore: added some more additional debug sanity checks * chore: added some more+ additional debug sanity checks * chore: mild log cleanup * chore: more log cleanup * chore: finish log cleanup * fix: added not null to migration so typeorm doesn't delete ids * chore: cleanup extra psql code * fix: remove eager load * docs: added documentation for migration to postgres * docs: added database option to bug template * feat: created docker-compose postgres file * fix: updated ts schema to align with change to migration * fix: switch timestamp to include timezone * fix: fixed indentation in psql docker-compose * fix: changed version to 0.1.0 to remove ui notification * style: fixed prettier in docker-compose.pastgres.yaml * chore: restored CHANGELOG.md * chore: revverted ts commit * fix: update pnpm lock with pg package * chore(pnpm-lock.yaml): updated pnpm-lock * docs: update docs to add psql set up info * refactor: clean up code from cr comments * feat: migrate blacklist * fix: fix issue with cypress tests * docs: update psql docs * fix: fix psql issue in user page; fix tiny psql error when selecting by empty list * fix: incorrect current date function * fix: null contraint with mediaAddedAt; fix psql col type * refactor: removed unnecessary import * feat: add postgres migration for streaming region --------- Co-authored-by: Fallenbagel <[email protected]> Co-authored-by: semantic-release-bot <[email protected]> Co-authored-by: zackhow <[email protected]> Co-authored-by: Ryan Algar <[email protected]> Co-authored-by: Ryan Algar <[email protected]>
🎉 This issue has been resolved in version 2.2.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hello, I did the following change: arch-anes/self-hosted-services@85f79eb without running any migrations. I started the installation from scratch. Upon container restart, I get the following error: But when I inspect the postgres db, I do see my user being created and the jellyfin token persisted in Do I still need to persist the config volume? Has |
settings.json will not be added to db. You should not be removing the volume. /app/config is not just to store db. There are many other things like logs and cached images and stuff |
I'm confused by the suggested command below to run pgloader with docker for migrating from sqlite to postgres after running jellyseerr once with postgres variables set. I don't have a
|
I feel like this defeats the purpose of this issue. The idea is to not require a persistent volume for important things like settings by using postgresql. Would you accept contributions to move (at least) the settings out of the json and into the db? |
@abelfodil that would be nice and feel free to discuss further here |
Description
I'd love to be able to connect Jellyseerr to an external MySQL or Postgres-compatible database to allow for sharding, replication, and HA deployments. Currently Jellyseerr (and Overseerr) uses an internal SQLite database for request storage.
Desired Behavior
Ideally, I'd like for there to be a set of environment variables that can be set in order to configure and use an external database connection. That way, the default (with no variables set) would be SQLite and no functionality is broken or removed for simple deployments like this. If the user so desires, they would be able to enable and configure the database, significantly expanding deployment options.
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: