This means that it would override MAIL_PASSWORD for any existing deploys right? Would be good if it can be backwards compatible as mentioned in #1 (not sure how, if you have any ideas)
This means that it would override MAIL_PASSWORD for any existing deploys right? Would be good if it can be backwards compatible as mentioned in #1 (not sure how, if you have any ideas)
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.
@@ -8,8 +8,9 @@ export SIGNING_SALT=$(cat /run/secrets/signing_salt)export ENCRYPTION_SALT=$(cat /run/secrets/encryption_salt)export SEEDS_PW=$(cat /run/secrets/seeds_pw)export LIVEBOOK_PASSWORD=$(cat /run/secrets/livebook_password)export MAIL_PASSWORD=$(cat /run/secrets/mail_password)This means that it would override MAIL_PASSWORD for any existing deploys right? Would be good if it can be backwards compatible as mentioned in #1 (not sure how, if you have any ideas)
Ah good point, I made the entrypoint backwards compatible by first checking if MAIL_PASSWORD exists
03d2fa21a6tof3c58df3c6