Darren Sisson

@sdezza no, you do not need any mounts here, if you need some files from your repo, just copy them in inside your dockerfile, all youre doing otherwise is overwriting...

@fguillen docker compose is a plugin, that automates running docker commands. Those commands are based on what is in the compose file. The default behaviour is to only pull images...

@Shreyaan-autonomix can you type env in command centre in preview container, if env are there then its next js build not picking them up, so next question would be is...

@andrasbacsai is this a bug? in ApplicationDeploymentJob.php ```php if ($this->pull_request_id === 0) { foreach ($this->application->build_environment_variables as $env) { if (data_get($env, 'is_multiline') === true) { $dockerfile->splice(1, 0, "ARG {$env->key}"); } else...

no i think runtime its fine, but build time there is a bug im sure of it, see above if you have dockerfile add a RUN env during build and...

 although i think the above it a bug in the code there is no bug in getting build vars in preview, so it must be your build path

@Shreyaan-autonomix out of interest are you using nixpacks?? well i tested nixpacks and i see preview build env vars during build there also. but any variables defined in a nixpacks...

@leodido #13 0.788 > echo "HOST_URL=$COOLIFY_FQDN" >> .env && cat .env #13 0.788 /*** ***/ #13 0.802 HOST_URL= i think ARG COOLIFY_FQDN would be needed to use it like this...

@leodido sorry, yes but what i mean is when that HOST_URL command is run, its ran inside the dockerfile nixpacks has created, but you would need to precede it with...

@Signum out of interest if you remove the volume from that part of the compose file, save then readd with the correct place does that work?