I'm wondering if something has changed in the more recent versions, previously I was able to over-ride the vagrant user and use a different account for SSH Auth using"
in the alm_root/config/deploy/production.rb file. But now it's trying to login using a vagrant user that doesn't exist (this installation was not done using vagrant). Where would it be getting the Vagrant user details from? And can I over-ride them?
Okay - worked it out, you can overwrite it using the .env file:
# user and group who own application repository
Yes, all configuration options were consolidated in the .env file in the 3.8 release. You can of course also use the
ENV variables directly, e.g.
DEPLOY_USER=someone_else bundle exec cap production deploy