-
Notifications
You must be signed in to change notification settings - Fork 79
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
[FR]Configure URL Base #95
Comments
I actually think this may just be a bug not a fr |
Hi @anothersmith! Thank you for reporting this :) Thank you! |
my-values.yaml
the configs are then generated like this;
I had expected the URL base to populate from the default values |
I am having the same issue, if i figure out how to resolve it ill post here |
Maybe a little late to the party, but I had this problem for a while and read through the initContainer function. In *arr-resources.yaml, the init container is this: apiVersion: v1
data:
config.xml: |
<Config>
<UrlBase>{{ .Values.sonarr.ingress.path }}</UrlBase> // here sets the UrlBase
</Config>
init-sonarr.sh: |
#!/bin/bash
echo "### Initializing config ###"
if [ ! -f /sonarr-config/config.xml ]; then
cp -n /init-sonarr/config.xml /sonarr-config/config.xml
echo "### No configuration found, intialized with default settings ###"
fi
kind: ConfigMap
metadata:
name: init-sonarr-cm This is supposed to save to a shared volume between that and the main container. This only gets created if we specify the container in our values file. So for me this'd look like radarr:
enabled: true
volume:
name: radarr-config
storageClassName: "local-path"
accessModes: ReadWriteOnce
storage: 5Gi Hope it helps. |
Ive been struggling to set this up for a while with sonarr and radarr just loading blank pages. Ended up having to deploy everything, jump on the NFS server update the url base in the configs and then restart the containers
Would be great if we could set this in the my-values.yaml file
The text was updated successfully, but these errors were encountered: