Deploying a new Gitea instance fails because of secret naming #10
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
abra app gitea_example_com secret generate --allfails because it tries to generate a secret called#secret_smtp_password-- i.e. it seemsabraisn't skipping commented-out lines properly.abra app gitea_example_com secret deployfails:secret_smtp_passwordis required, because it's referenced in the maincompose.ymlfile -- it would be nice if this were optional, as not everyone will need to provide an SMTP password. If it isn't optional, we should uncomment it in.env.sample.env.samplehavePASSWORD, where thecompose.ymlfile is looking forpasswdAha! Made https://git.autonomic.zone/coop-cloud/abra/issues/133. Also see
cb8e0a819b/compose.yml (L92-L93)(was putting this off because of the busywork of migrating our own instance). Making the SMTP password optional is definitely a good idea. There is some config to wrap in a conditional also. Probably other things could be made optional.This is resolved now :) https://git.autonomic.zone/coop-cloud/abra/issues/133 is still outstanding but now that the SMTP configurations are totally optional, things are only generated when needed.