From 85494de2707f2e45cc805119602051ca67e43a0f Mon Sep 17 00:00:00 2001 From: Andrew Austin Date: Thu, 3 Nov 2022 21:31:45 -0500 Subject: [PATCH] Allow RELEASE_NAME to be overridden in environment (#1087) RELEASE_NAME was locked to a static value which prevented multiple instances of Firezone from running in the same network namespace (i.e. using net=host in a container). This change uses the value of the RELEASE_NAME environment variable and defaults to the current static value if not set. --- rel/env.sh.eex | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/rel/env.sh.eex b/rel/env.sh.eex index 86e387fb2..2349868fe 100644 --- a/rel/env.sh.eex +++ b/rel/env.sh.eex @@ -15,7 +15,10 @@ # the one below (my_app@127.0.0.1), you need to also uncomment the # RELEASE_DISTRIBUTION variable below. Must be "sname", "name" or "none". export RELEASE_DISTRIBUTION=name -export RELEASE_NODE=<%= @release.name %>@127.0.0.1 +# RELEASE_NAME is guaranteed to be set by the start script and defaults to 'firezone' +# set RELEASE_NAME in the environment to a unique value when running multiple instances +# in the same network namespace (i.e. with host networking in Podman) +export RELEASE_NODE=$RELEASE_NAME@127.0.0.1 # Choices here are 'interactive' and 'embedded'. 'interactive' boots faster which # prevents some runit process management edge cases at the expense of the application