search

sct / overseerr

Request management and media discovery tool for the Plex ecosystem
https://overseerr.dev
MIT License
3.76k stars 437 forks source link

Overseer configuration via configuration file/s #3472

Open AurimasNav opened 1 year ago

AurimasNav commented 1 year ago

Description

When deploying overseerr all the configuration must be done via webgui, it would be great if we could have a way to define all the configuration outside the webgui, so it is reusable.

Desired Behavior

Any config file would do, so we can mount it and be done with it.

Additional Context

I've reinstalled my home server recently and reconfiguring things via webgui is a pain, there are countless mistakes and details being forgotten, going back and forth until everything is restored to how it was. Being able to reuse config files saved in git would be great improvement, not only for redeployments, but also for sharing config with others.

Code of Conduct

TheCatLady commented 1 year ago

Overseerr settings are already stored in a JSON file.

AurimasNav commented 1 year ago

Is there a way to pass in some values as env variables?

thde commented 1 year ago

If not possible, you could run something like this in an entrypoint before starting overseerr to configure certain keys with ENV variables:

$ jq 'with_entries( .value = ($ENV[.key] // .value) )' /app/config/config.json > /app/config/config.json

https://unix.stackexchange.com/a/657596

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

hirenshah commented 1 year ago

Unstale

stale[bot] commented 11 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

danshilm commented 5 months ago

The settings configuration file mounted at /app/config/settings.json accomplishes what the original author would like. As for setting them via environment variables, there are too many options to set to allow changing them with environment variables. However, the port number, for example, used for the application is configurable with an environment variable PORT, but apart from that, I really don't see a scenario where configuring Overseerr would be done with only environment variables.

Please share the scenario you had in mind if possible.