I’m using edeliver and distillery to build the app on the build host.
I have tried so many things to make sure my environment variables get compiled while the release is being built on the build host but it seems not work.
I added this snippet to my .deliver/config
status "Configuring Environment Variable"
local _environment_var_path="/home/deploy/.env"
__sync_remote "
ln -sfn '$_environment_var_path' '$BUILD_AT/.env'
cd '$BUILD_AT'
source .env
“
Do you get an error message? Which one? Is something deployed to your remote but it fails to start? Or crashes after a couple of seconds without beeing hit by requests?
Sorry, I misunderstood the question…
Long story short: :extwitter doesn’t seem to understand the :system-tuple.
as you can see, you are triying to link a file with the literal name $_environment_var_path to a file called literally .env in a folder called literally $BUILD_AT, into which you also cd. Even if the targets could work, they will probably not as you expect it The source though does definitifely not work, I can’t imagine a file $_environment_var_path to exist in your pwd…
OK, I see. Also I do see now, that they are expanded locally.
So, if you do those steps manually on your server, does it work then? do you see any error messages in the process? Can you log in edeliver which commands are actually sent to the remote site?