-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.env problem #87
Comments
In Also, since you're deploying to prod you should move |
I confirm that changing |
I've hit this problem too. A note is by doing the change in the repo copy it's going to copy the full .git directory over too. Instead since often you don't want all your dotfiles copied it'd be better to use beforePreparing:
|
the /release directory doesn't contain .env file while /repo dir has this .env file |
Could I please describe this issue in documentation? I confused about best practices of managing .env when I using this bundle. I was trying
and
But both does not works. In case of default config
I obtaining
Because of |
This works for me.
|
Hi, On my side I prefer :
|
For Symfony 4.3 it should be copy .env to .env.local
…On Wed, Jul 17, 2019, 2:44 PM Nicolas Guillard ***@***.***> wrote:
Hi,
On my side I prefer :
public function beforePreparing() { $this->log('<h3>Copying over the .env
files</>'); $this->runRemote('cp {{ deploy_dir }}/repo/.env.dist {{
project_dir }}/.env'); }
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#87?email_source=notifications&email_token=AKMP3X5HWWYVCTWI5O7EGE3P74H4NA5CNFSM4GTAYAKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ECEDQ#issuecomment-512238094>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKMP3XZJ7GYINMMFOCHDUATP74H4NANCNFSM4GTAYAKA>
.
|
The deploy script don't seems to copy dot files on project root folder, is that only for me ? |
I also faced this issue. The drawback is that you now have to handle manually the change in your .env file as it won't be synchronized with your repo, but anyway you would have to edit your .env.local file. No big deal. |
Hello, I have also to put the .env as a shared file. Check out https://stackoverflow.com/q/59111354/633864, in fact I don't need to use env vars as my application only relies on .env files. Do you think I would be ok to introduce a new parameter to see if the APP_ENV env should be set? |
This fixes issues like EasyCorp#87 ``` Unable to read the "... .env" environment file. in ... ```
Using Symfony 5 with PHP 7.4, this PR #114 fixes that issue. |
I thought we shouldn't commit any secrets in |
This fixes issues like EasyCorp#87 ``` Unable to read the "... .env" environment file. in ... ```
Hi,
I have
$this->runRemote('export SYMFONY_ENV=prod');
but uppon deploy error
PHP Fatal error: Uncaught Symfony\Component\Dotenv\Exception\PathException: Unable to read the "/var/www/vhosts/iwebi.pl/app-s4.iwebi.pl/releases/20190129153613/.env" environment file. in /var/www/vhosts/iwebi.pl/app-s4.iwebi.pl/releases/20190129153613/vendor/symfony/dotenv/Dotenv.php:466
butr
The text was updated successfully, but these errors were encountered: