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

wordmove push -a and/or -w no working / -d is fine #258

Closed webitekt closed 8 years ago

webitekt commented 8 years ago

Hi,

I successfully installed wordmove and also the Movefile. Pushing the db is working.

trying to push the whole installation ends up with an error. command: wordmove push -e staging -all OR wordmove push -e staging -a ERROR: "wordmove push" was called with arguments ["-a"]

command: wordmove push -e staging -w /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/deployer/base.rb:110:in push_wordpress': undefined methodpush' for "...":String (NoMethodError) from /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/cli.rb:60:in block in push' from /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/cli.rb:36:inblock in handle_options' from /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/cli.rb:34:in each' from /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/cli.rb:34:inhandle_options' from /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/cli.rb:59:in push' from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/command.rb:27:inrun' from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command' from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:359:indispatch' from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/base.rb:440:in start' from /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/exe/wordmove:6:in<top (required)>' from /usr/local/bin/wordmove:23:in load' from /usr/local/bin/wordmove:23:in

'

I already updated gem.

Any hint is appreciated.

mukkoo commented 8 years ago

Hi @webitekt the flag -a or -all doesn't exists. You must to use --all flag.

The problem with "...":String (NoMethodError) seems is related to some syntax error(s) in your Movefile. Default Movefile (generated with wordmove init) contains

staging: # multiple environments can be specified [...]

I suggest you to check this and reopen the issue if needed.