Elio Bischof

> CC @eliobischof: when this is released the milestone projection will look like: > > ```sql > CREATE TABLE IF NOT EXISTS projections.milestones2 > ( > instance_id text COLLATE pg_catalog."default"...

@Lite5h4dow we decided to push the idea of using subcharts with the cert job to the backlog for now. There are pros and cons, and we'd like to figure out...

> Hi, @eliobischof > > Thanks, happy to contribute. > > Re: string -> int > > this was my initial instinct too, but I didn't do it because of...

You can pass multiple config files to the zitadel binary. Something like `zitadel start-from-init --config bind-mounted-zitadel.yaml --config from-docker-secret-zitadel.yaml` https://zitadel.com/docs/self-hosting/manage/configure#configure-by-files Please reopen the issue if that doesn't help.

Could you clarify what prevents you from defining all secret values in a YAML string, placing it into a Docker secret, mounting it inside the container, and passing it to...

> If I do get that working alright, I could share an example compose file in a PR to add to the docs. That would be really great, thank you...

> I stopped my review as I fail to see a reason why we needed to create a whole release.ts and why we need to use gh upload to upload...

> > How would you upload the release assets? There is no Nx Release standard for this. > > Got it, but would it not be easier to rely on...

> Ok, I see where you are coming from but I am still worried about having multiple tools to create artifacts and push them to multiple different stores (docker, npm,...

Probably we still need the monorepo graph capabilities from `nx release version`. But I'll try to switch to semantic release to actually publish the artifacts and further reduce custom logic...