The Capistrano 3 guide recommends the use of passwordless sudo. This allows your less-priveleged user execute the sudo command without having to enter a password via the PTY. You can use the task that Kentaro wrote above, and add something like the following to your /etc/sudoers file: deploy ALL=NOPASSWD:/bin/cp ~/something /something http://www.capistranorb.com/documentation/getting-started/authentication-and-authorisation/#toc_8
Smells like a Cap 3 bug. I suggest just guaranteeing you are where you want to be from the shell perspective: execute “cd ‘#{release_path}’; #{fetch(:composer_command)} install”
Do you have your ssh key added to the list of agent identites ? You can check with ssh-add -L , you should see the key your are using to connect to github : $ ssh-add -L ssh-rsa AAAAB3N…..0VmSiRvTzBrbU0ww== /Users/youruser/.ssh/id_rsa If you don’t see the ssh key you use for github or a message like … Read more
This does the trick for me, it collects the public ssh keys on the nodes and distributes it over all the nodes. This way they can communicate with each other. – hosts: controllers gather_facts: false remote_user: root tasks: – name: fetch all public ssh keys shell: cat ~/.ssh/id_rsa.pub register: ssh_keys tags: – ssh – name: … Read more
You can restart manually using the following command bundle exec pumactl -P /home/deploy/.pids/puma.pid restart Make sure you point to the correct pid path.
You might be best looking at the difference between ENVIRONMENT VARIABLES and SHELL VARIABLES When you fire SSH, your app will load the SHELL variables which are defined in your .bashrc file. These only exist for the life of the shell, and therefore, we don’t use them as much as ENV vars You may be … Read more
In Capistrano v3, you must specify where you want to run the code by calling on with a list of hostnames, e.g. task :execute_on_server do on “root@example.com” do execute “some_command” end end If you have roles set up, you can use the roles method as a convenience: role :mailserver, “root@mail.example.com” task :check_mail do on roles(:mailserver) … Read more
I had the same issue, until I realized I was pulling the nonexistent branch from git.