[Feature Request] Add support for external database connections

[mari-arondeus]

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

• [X] I agree to follow Overseerr's Code of Conduct

[teambvd]

+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!

[aleksasiriski]

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

[teambvd]

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!

[joaopedrocg27]

Is there any update for this? It is a dealbreaker for K8s users