Using Deployer. After provisioning my droplet, I try to deploy but the wrong db credentials are being used. Interestingly the correct credentials are set in both .env and .env.example. I try to clear my cache, but get a mysql error access denied for deployer@localhost. I'm assuming this is trying to access my local mysql, and not the remote mysql on my droplet. I could probably fix this by sshing into the droplet and fixing the .env, but I am wondering why this is happening.
#Deployer not reading env changes
patent pagoda
late crag
Nah I'm pretty sure it's on the remote. But is it the right host? Try "dep ssh {name}" (name from deploy.php) and see if you end up on the expected server. Check if you can run the artisan commands manually.
Also don't put secrets in .env.example. It's meant to be a git tracked template, showing which env variables the app requires.