search

welaika / wordmove

Multi-stage command line deploy/mirroring and task runner for Wordpress
https://wptools.it/wordmove
MIT License
1.87k stars 167 forks source link

Cannot Pull Uploads #384

Closed sbehnfeldt closed 6 years ago

sbehnfeldt commented 7 years ago

I can pull my database from my staging site to my local site: wordmove pull -d -e staging

But I can't pull my uploads: wordmove pull -u -e staging

Amongst the output I see, "The source and destination cannot both be remote."

I do notice that the rsync command line includes a colon in front of the staging site's path: :/home/username/web/staging/public/wp-content/uploads even though in my wordmove file the wordpress_path for my staging site does not include this. I tried executing the rsync manually from my local Windows command prompt and got the same error, but when I removed the colon I got a login prompt. (Login failed, presumably for other reasons.)

Wordmove 2.0.0 on Windows 10 local, Linux remote

alessandro-fazzi commented 7 years ago

Could you post your Movefile, please?

sbehnfeldt commented 7 years ago

Movefile-Redacted.txt

sbehnfeldt commented 7 years ago

Any progress on this?

alessandro-fazzi commented 7 years ago

The only thing I could do is to ask you if you have tried with the latest Wordmove version: we have fixed some bugs here and there and moreover we have changed a bit inside a dependency https://github.com/welaika/photocopier/commit/ae80a921ba8e8822e3cc67cac3dd965f3c24cb2f which should be on the path on your problem.

That said: I can't test on Windows and I can't reproduce. It'd be beautiful if some Windows users from the community could take a little ride on this...

truwo commented 7 years ago

I'm experiencing the very same using wordmove 2.1.3 inside vagrant vm using Ubuntu 14.04.5. My machine is running OSX. The very same happens not only for uploads, but for all pulls of file related stuff, where rsync command is issued similarly with different paths. The colon is only put to the front of the source path, not to the front of the target path of rsync.

This is the rsync command that fails (here for themes):

rsync --progress -e 'sshpass -p vagrant ssh vagrant@wz.dev' -rlpt --compress --omit-dir-times --delete --exclude .git/ --exclude .gitignore --exclude .sass-cache/ --exclude node_modules/ --exclude bin/ --exclude tmp/* --exclude Gemfile* --exclude Movefile --exclude wp-config.php --exclude wp-content/*.sql :/srv/www/wz-dev/htdocs/wp-content/themes/ /srv/www/local-dev/htdocs/wp-content/themes

alessandro-fazzi commented 6 years ago

@truwo Wordmove always consider one stage the local one and the other a remote one.

You can't work outside of the vagrant box with wordmove and perform a pull/push operation across to "remote" machines.

The colon is put where wordmove considers the stage to be remote. Open an ad hoc issue if you need.

Going to close this one because abandoned.

Cheers