You don’t need to set the cookie yourself unless you need to conveniently know it externally like connecting from your local iex. In such cases you can still fly ssh console
and lookup the generated cookie out of the release. If you want to maintain your current cookie setup via env, you can pass it along to the FLAME’s using the :env
backend option:
if config_env() == :prod do
config :flame, :backend, FLAME.FlyBackend
config :flame, FLAME.FlyBackend,
token: System.fetch_env!("FLY_API_TOKEN"),
env: %{"RELEASE_COOKIE" => System.fetch_env!("RELEASE_COOKIE")}
end