You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.
I have a Laravel .env file that needs to be shared between releases. I put the .env file in shared folder as well as shared in 'remote.php'.
After the deploy event I tell my nginx container to refresh its internal code base with the latest at 'current'. The files all mount properly into the container except for .env as its symlinked in the host container.
Would the best solution be to just manually copy the files in the deploy after instead of using the 'shared' functionality?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a Laravel .env file that needs to be shared between releases. I put the .env file in shared folder as well as shared in 'remote.php'.
After the deploy event I tell my nginx container to refresh its internal code base with the latest at 'current'. The files all mount properly into the container except for .env as its symlinked in the host container.
Would the best solution be to just manually copy the files in the deploy after instead of using the 'shared' functionality?
The text was updated successfully, but these errors were encountered: