You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is respected by capistrano-wpcli, but unfortunately it is used the same way on local as well, which results in following error for me:
| => bundle exec cap production wpcli:uploads:rsync:pull
INFO [29d88580] Running /usr/bin/env rsync -avz --rsh=ssh --progress [email protected]:/www/itvar.cz/wwwroot/www/shared/web/app/uploads/ web/app/uploads/ as Cibulka@localhost
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Command::Failed: rsync exit status: 65280
rsync stdout: Nothing written
rsync stderr: ssh: connect to host 81.91.83.149 port 22: Operation timed out
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-45/rsync/io.c(453) [receiver=2.6.9]
Tasks: TOP => wpcli:uploads:rsync:pull
(See full trace by running task with --trace)
Is it possible to make capistrano-wpcli use different command on production (/home/web720/composer.phar) and development (composer)?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
And yes, you are right - the main issue is with port 22. So I guess that before dealing with development/production command for Composer (composer//home/web720/composer.phar) I need to resolve the issue with the port setting.
Because of that, do you have any updates on #28? Thank you!
In my production server, I can't install stuff globally. Because of that, in my
deploy/production.rb
file, I have the following config:This is respected by
capistrano-wpcli
, but unfortunately it is used the same way on local as well, which results in following error for me:Is it possible to make
capistrano-wpcli
use different command on production (/home/web720/composer.phar
) and development (composer
)?Thanks in advance!
The text was updated successfully, but these errors were encountered: