You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
I like to use PGO operator for all Postgres databases as it offers out-of-the-box upgrades, database backups, point-in-time restores etc. I would really like to use a PGO managed database for paperless-ngx, so I miss the option to use an external database in this helm chart.
Ideally would be an additional structure in the values.yaml like this:
With this example one could define wether to use an external database or not, and then chose from either using the values from the host, userName, password and other values, or to refer to an EXISTING secret and the keys within this secret being used. If one key would not be defined to be used in the existing secret, the appropriate "direct" option would be used, then.
Would a PR for such a feature be well received?
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
At the moment, this is doable by setting the Paperless-ngx database envs. I wouldn't be opposed to adding Helm values if more people prefer configuring them this way, but I usually try to keep the number of config values to a minimum in these charts. That keeps things simpler, and since the bjw-s common chart supports using hardcoded envs, valueFrom references, or envFrom, it's has been configurable enough for my use.
Chart Name
paperless-ngx
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
I like to use PGO operator for all Postgres databases as it offers out-of-the-box upgrades, database backups, point-in-time restores etc. I would really like to use a PGO managed database for paperless-ngx, so I miss the option to use an external database in this helm chart.
Ideally would be an additional structure in the values.yaml like this:
With this example one could define wether to use an external database or not, and then chose from either using the values from the
host
,userName
,password
and other values, or to refer to an EXISTING secret and the keys within this secret being used. If one key would not be defined to be used in the existing secret, the appropriate "direct" option would be used, then.Would a PR for such a feature be well received?
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: