Local Docker Compose Development: How to Bootstrap Zitadel with default settings?
Original message was deleted
Rhi @maaft Interesting usecase 
I will check with my team
you can definitely start a zitadel instance with a service user pre configured, more about it is written here
https://zitadel.com/docs/self-hosting/deploy/compose#docker-compose-with-service-account
but for rest of the points, I have to check
I will check with my team
you can definitely start a zitadel instance with a service user pre configured, more about it is written here
https://zitadel.com/docs/self-hosting/deploy/compose#docker-compose-with-service-account
but for rest of the points, I have to check
Rhi @maaft I looked more into it and it seems like for now you can bootstrap your zitadel instances with these options mentioned here
https://github.com/zitadel/zitadel/blob/main/cmd/setup/steps.yaml
that is how it is for now, I will check with m engineers if we can extend it to create/include a default project(project name like you mentioned) btu for the rest(app config and recieve service user JWT) I am not sure if this could be a possibility(design constraint probably) nevertheless I will check it with them
https://github.com/zitadel/zitadel/blob/main/cmd/setup/steps.yaml
that is how it is for now, I will check with m engineers if we can extend it to create/include a default project(project name like you mentioned) btu for the rest(app config and recieve service user JWT) I am not sure if this could be a possibility(design constraint probably) nevertheless I will check it with them
GitHub
ZITADEL - Identity infrastructure, simplified for you. - zitadel/zitadel
SWhat's the issue with creating the missing parts via API calls?
SIf you really don't want it to be API calls executed outside containers (in a script file), you could still make it a bootstrap/ init container. For development that should okay.
Rhi @maaft glad it worked out, if that helped please mark the answers with 
to close it
to close it