How to configure a static/known/repeatable developer environment?
āļøConfigurationš¬Self-hostedāQuestionā
Solved
I am trying to configure a local developer environment.
Currently I am using docker/compose to start the infrastructure services (postgres, zitadel, traefik, redis, rabbitmq, grafana, etc) and then using terraform to setup a default org/project/app. Now I would like to be able to have the developers use the client_id/client_secret easily. I was wondering how other peoploe are doing this.
For example, whenever the developer starts fresh (deletes their docker volumes) they need to update the client_id/client_secret they are using.
Also, I would like to enable OIDC in rabbitmq and grafana so they can log into the management consoles for those with their zitadel account. However, those require the client_ids of their respective apps which is generated dynamically so it's hard to configure this.
Currently I am using docker/compose to start the infrastructure services (postgres, zitadel, traefik, redis, rabbitmq, grafana, etc) and then using terraform to setup a default org/project/app. Now I would like to be able to have the developers use the client_id/client_secret easily. I was wondering how other peoploe are doing this.
For example, whenever the developer starts fresh (deletes their docker volumes) they need to update the client_id/client_secret they are using.
Also, I would like to enable OIDC in rabbitmq and grafana so they can log into the management consoles for those with their zitadel account. However, those require the client_ids of their respective apps which is generated dynamically so it's hard to configure this.
