env values not reflected in provisioned server #4193
Replies: 2 comments
-
|
run dep deploy -v |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I was able to fix the issue using dep deploy --branch feature/name |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Using v8.0.0-beta for Laravel.
Just started using Deployer, and I am running into an issue during migration during the 'dep deploy' stage. Access is denied for root@localhost. In both .env and .env.example and during the 'dep init' stage, I specified my db user as deployer (default) with no password. When I ssh into my Droplet, the .env values show up as 'root'.
I could change these values manually, but wonder why the local env values are not used on server.
For reference I cloned my repo locally, then locally ran dep init & provision successfully on server, but failed dep deploy. Clearing cache fails when searching for the deployer user on local mysql.
edit: changing db user/pw to user/user in .env, clearing cache, and using user/user during 'dep provision', this resulted in the server's env using root/no pw. Not sure why the mysql user/pw is not being affected. Is deployer using the master branch? I am on a feature branch.
Beta Was this translation helpful? Give feedback.
All reactions