Move user release config to user directory (#2302)

docs/deployment/docker.md

@@ -62,4 +62,4 @@ When clustering is enabled, you must additionally set the following env vars:
 
 `LIVEBOOK_DISTRIBUTION` is automatically set to `name` if clustering is enabled.
 
-Some variables, like `LIVEBOOK_NODE`, are oftentimes computed at runtime. When using the Livebook Docker image, you can create a file at `/app/env.sh` that exports the necessary environment variables. This file is invoked right before booting Livebook.
+Some variables, like `LIVEBOOK_NODE`, are oftentimes computed at runtime. When using the Livebook Docker image, you can create a file at `/app/user/env.sh` that exports the necessary environment variables. This file is invoked right before booting Livebook.

lib/livebook/hubs/dockerfile.ex

@@ -134,7 +134,7 @@ defmodule Livebook.Hubs.Dockerfile do
           export ERL_AFLAGS="-proto_dist inet6_tcp"\n\
           export LIVEBOOK_NODE="${FLY_APP_NAME}-${FLY_IMAGE_REF##*-}@${FLY_PRIVATE_IP}"\n\
           export LIVEBOOK_CLUSTER="dns:${FLY_APP_NAME}.internal"\n\
-          ' > /app/env.sh
+          ' > /app/user/env.sh
           """
       end
 

rel/server/env.bat.eex

@@ -1,5 +1,5 @@
-if exist "!RELEASE_ROOT!\env.bat" (
-  call "!RELEASE_ROOT!\env.bat"
+if exist "!RELEASE_ROOT!\user\env.bat" (
+  call "!RELEASE_ROOT!\user\env.bat"
 )
 
 set RELEASE_MODE=interactive

rel/server/env.sh.eex

@@ -1,5 +1,5 @@
-if [ -f "${RELEASE_ROOT}/env.sh" ]; then
-  . "${RELEASE_ROOT}/env.sh"
+if [ -f "${RELEASE_ROOT}/user/env.sh" ]; then
+  . "${RELEASE_ROOT}/user/env.sh"
 fi
 
 export RELEASE_MODE=interactive