foxgirlriley/kubernetes-service-repo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(documentation): Added mealie readme content and adjusted config

Browse source
This commit is contained in:
Fishandchips321 2026-04-15 14:55:48 +01:00
parent 7c8a584b75
commit 15ce4b1e30
3 changed files with 37 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

9
Mealie/README.md
View file

@ -0,0 +1,9 @@
# Mealie
Mealie is a recipe management service with features for creating shopping lists from recipes and a meal planner.
## Using this kubernetes config
Firstly, you will need to create a generic kubernetes secret with the database username and password. You can do this with the command `kubectl create secret generic mealie-db --from-literal=username=<username here> --from-literal='password=<password here>'`. Make sure to use a secure password.
Then you will need to set mealie's hostname in `deployment.yml` under the env variables and in `ingress.yml`. Ensure the one in `deployment.yml` contains `https://` and that the one in `ingress.yml` is just the hostname (no `https://`). This config assumes you have cert-manager installed on your cluster, so if you want to provide HTTPS another way, feel free to comment out the `spec.tls` section (the annotation shouldn't affect anything, but you can comment it out as well if you want)
If you want to use OIDC to log into mealie, uncomment the OIDC environment variables and fill in the provider name and OIDC configuration url (the one with `.well-known/...` in the path). [put here a section about what callback urls to use in your provider]. Also, create another kubernetes generic secret to hold the OIDC sensitive config. You can do this with the command `kubectl create secret generic mealie-oidc --from-literal=client-id=<OIDC client ID> --from-literal=client-secret=<OIDC client secret> --from-literal=admin-group=<OIDC group for mealie admins>`