To avoid having to set all the secrets even when you don't use them, I've split everything out into seperate compose files.
Some things are now set as secrets when they were just env vars before, so they will need new secrets setting...
POSTAL_API_KEY var -> postal_api_key secret
To avoid having to set all the secrets even when you don't use them, I've split everything out into seperate compose files.
Some things are now set as secrets when they were just env vars before, so they will need new secrets setting...
- POSTAL_API_KEY var -> postal_api_key secret
Great, will merge and release. I'll add a release note as existing installations will need to reconfigure before deploying it, to add the extra compose files in, if they use other features.
Great, will merge and release. I'll add a release note as existing installations will need to reconfigure before deploying it, to add the extra compose files in, if they use other features.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
To avoid having to set all the secrets even when you don't use them, I've split everything out into seperate compose files.
Some things are now set as secrets when they were just env vars before, so they will need new secrets setting...
Was just able to get an instance up with these defaults 🥳
Great, will merge and release. I'll add a release note as existing installations will need to reconfigure before deploying it, to add the extra compose files in, if they use other features.