File ends up in shared even though not configured #4039
|
So I have an env file which holds only the current release version. Therefore, it should not be in the shared folder and symlinked because then all releases will be reading the same version. Here is my shared file/folder config: add('shared_files', ['.env', 'config/gireve/gireve.crt.pem', 'config/gireve/gireve.key.pem']);
add('shared_dirs', ['var/log']);And this is the job that writes the current version to task('app:set-version', function () {
within('{{release_path}}', function () {
run('echo "APP_VERSION={{release_revision}}" > {{release_path}}/.env.local');
});
});I have completely deleted the .env.local from the servers and ran the deploy again. To my amazement, it still came back as symlinked file from the shared folder 😱. What am I missing here? 😅 Some unexpected behaviour perhaps? |
Answered by
antonmedv
Mar 22, 2025
Replies: 1 comment 6 replies
|
Run deploy with -v to see what commands are executed. |
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Try using set, instead of add