Phoenix app uses a different erlang distribution cookie between deploys

Hello! I have a basic Phoenix app with a SECRET_KEY_BASE set. I’m deploying this as a fleet of containers, and would like to be able to add/remove containers without redeploying the whole sheban.

It seems like the erlang distribution cookie changes if I deploy, then deploy again a few hours later. Is this expected, or have I configured my app wrong? Assuming it’s supposed to be doing that, can I give it a more permanent cookie with an environment variable?

You can set RELEASE_COOKIE environment variable to keep it between deployments.


Oh nice, thanks. Would you believe I looked for that and couldn’t find it? :smiley:

1 Like