studio/people
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
This repository has been archived on 2026-03-24. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
dd8bd2a89b39240d583c5edc45b6c2d8cd5c7286
people/src/helm/env.d/dev/values.desk.yaml.gotmpl

95 lines
2.7 KiB
Go Template
Raw Normal View History

🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
image:
repository: localhost:5001/people-backend
pullPolicy: Always
tag: "latest"
backend:
🔨(CI) add Tilt Tilt is a tool for local Kubernetes development. It makes it easy to see your changes as you make them, and it rebuilds and redeploys your app as you change it.
2024-06-03 10:05:45 +02:00
replicas: 1
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
envVars:
🩹(helm) rename mismatching environment variable CSRF trusted origins are set using an environment variable. The env value was wrongly name to CORS_ALLOWED_ORIGINS, which doesn't exist in our Django configurations. I fixed this minor issue.
2024-03-19 09:59:19 +01:00
DJANGO_CSRF_TRUSTED_ORIGINS: https://desk.127.0.0.1.nip.io,http://desk.127.0.0.1.nip.io
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
DJANGO_CONFIGURATION: Production
DJANGO_ALLOWED_HOSTS: "*"
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
DJANGO_SECRET_KEY:
secretKeyRef:
name: backend
key: DJANGO_SECRET_KEY
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
DJANGO_SETTINGS_MODULE: people.settings
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
DJANGO_SUPERUSER_PASSWORD:
secretKeyRef:
name: backend
key: DJANGO_SUPERUSER_PASSWORD
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
DJANGO_EMAIL_HOST: "mailcatcher"
DJANGO_EMAIL_PORT: 1025
🐛(helm) enable SSL when sending email Email settings were wrongly configured. It led to unsent email and timeout response from the backend server. I forgot to enable the SSL while using the Email service from scalingo.
2024-03-27 10:31:35 +01:00
DJANGO_EMAIL_USE_SSL: False
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
OIDC_OP_JWKS_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/jwks
OIDC_OP_AUTHORIZATION_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/authorize
OIDC_OP_TOKEN_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/token
OIDC_OP_USER_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/userinfo
🔧(helm) setup logout flow from Agent Connect Add the relevant environment configurations to make sure the backend in dev and staging environments log out the user from Agent Connect.
2024-04-10 00:19:20 +02:00
OIDC_OP_LOGOUT_ENDPOINT: https://fca.integ01.dev-agentconnect.fr/api/v2/session/end
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
OIDC_RP_CLIENT_ID:
secretKeyRef:
name: backend
key: OIDC_RP_CLIENT_ID
OIDC_RP_CLIENT_SECRET:
secretKeyRef:
name: backend
key: OIDC_RP_CLIENT_SECRET
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
OIDC_RP_SIGN_ALGO: RS256
OIDC_RP_SCOPES: "openid email"
OIDC_REDIRECT_ALLOWED_HOSTS: https://desk.127.0.0.1.nip.io
OIDC_AUTH_REQUEST_EXTRA_PARAMS: "{'acr_values': 'eidas1'}"
LOGIN_REDIRECT_URL: https://desk.127.0.0.1.nip.io
LOGIN_REDIRECT_URL_FAILURE: https://desk.127.0.0.1.nip.io
🔧(helm) setup logout flow from Agent Connect Add the relevant environment configurations to make sure the backend in dev and staging environments log out the user from Agent Connect.
2024-04-10 00:19:20 +02:00
LOGOUT_REDIRECT_URL: https://desk.127.0.0.1.nip.io
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
DB_HOST: postgres-postgresql
DB_NAME: people
DB_USER: dinum
DB_PASSWORD: pass
DB_PORT: 5432
POSTGRES_DB: people
POSTGRES_USER: dinum
POSTGRES_PASSWORD: pass
🚀(helm) add a Redis cache service This commit is working in progress. I have added an extra chart to take benefits of the Redis operator developed by Indie hoster. When using the dev environment, I used bitnami redis chart to deploy a Redis service with authentication disable.
2024-03-19 13:36:50 +01:00
REDIS_URL: redis://default:pass@redis-master:6379/1
✨(mailboxes) add mail provisioning api integration We want people to create new mailboxes in La Régie. This commit adds integration with intermediary dimail-api, which will in turn send our email creation request to Open-Xchange.
2024-08-05 12:20:44 +02:00
MAIL_PROVISIONING_API_URL: "http://host.docker.internal:8000"
🔧(helm) fix mail provisioning env I forgot to use the new variable on the deployment.
2024-09-10 16:20:30 +02:00
MAIL_PROVISIONING_API_CREDENTIALS:
secretKeyRef:
name: backend
key: MAIL_PROVISIONING_API_CREDENTIALS
📈(monitoring) configure sentry dsn configure sentry dsn to monitor errors in sentry
2024-09-04 18:00:39 +02:00
SENTRY_DSN: "https://b72746c73d669421e7a8ccd3fab0fad2@sentry.incubateur.net/171"
🔨(CI) add Tilt Tilt is a tool for local Kubernetes development. It makes it easy to see your changes as you make them, and it rebuilds and redeploys your app as you change it.
2024-06-03 10:05:45 +02:00
command:
- "gunicorn"
- "-c"
- "/usr/local/etc/gunicorn/people.py"
- "people.wsgi:application"
- "--reload"
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
👷(helm) command createsuperuser We need a superuser in the Django application, to have access to the admin part. This commit create a superuser on the pods.
2024-06-19 10:39:18 +02:00
createsuperuser:
command:
- "/bin/sh"
- "-c"
🐛(helm) fix createsuperuser command The createsuperuser command changes recently. We update the command to reflect the changes.
2024-06-28 11:20:57 +02:00
- python manage.py createsuperuser --username admin@example.com --password admin
👷(helm) command createsuperuser We need a superuser in the Django application, to have access to the admin part. This commit create a superuser on the pods.
2024-06-19 10:39:18 +02:00
restartPolicy: Never
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
frontend:
🔨(CI) add Tilt Tilt is a tool for local Kubernetes development. It makes it easy to see your changes as you make them, and it rebuilds and redeploys your app as you change it.
2024-06-03 10:05:45 +02:00
envVars:
PORT: 8080
♻️(frontend) frontend environment free Until now, the front had to know at build time the url of the backend and the webrtc server to be able to communicate with them. It is not optimal because it means that we need multiple docker image (1 per environment) to have the app working, it is not very flexible. This commit will make the frontend "environment free" by determining these urls at runtime.
2024-06-03 12:53:23 +02:00
NEXT_PUBLIC_API_ORIGIN: https://desk.127.0.0.1.nip.io
🔨(CI) add Tilt Tilt is a tool for local Kubernetes development. It makes it easy to see your changes as you make them, and it rebuilds and redeploys your app as you change it.
2024-06-03 10:05:45 +02:00
replicas: 1
command:
- yarn
- dev
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
image:
repository: localhost:5001/people-frontend
pullPolicy: Always
tag: "latest"
ingress:
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
enabled: true
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
host: desk.127.0.0.1.nip.io
🐛(helm) fix wrongly named ingress Admin ingress has been partially renamed to ingressAdmin. I forgot to update helmfile values. Fixed them.
2024-03-21 17:37:52 +01:00
ingressAdmin:
🚀(helm) support Django Admin pages in ingress paths Based on @rouja reco, I added a dedicated ingress to serve Django Admin pages and Django statics. The admin route will be secured by the oauth proxy. I simply copy/pasted the first ingress template, and adapted it.
2024-03-20 15:22:22 +01:00
enabled: true
host: desk.127.0.0.1.nip.io
Reference in New Issue Copy Permalink