Multi-stage command line deploy/mirroring and task runner for Wordpress
mu-plugins. Now it is fixed (thanks to @seanclen)ed25519 ssh keysWordmove::Hook::Local and Wordmove::Hook::Remote in how the class' logger was defined.Due to a stupid error I immediately released 5.2.1 after 5.2.0. I'm sorry about that. This is why you won't find 5.2.0's relase notes.
Hello everybody!
I'm particularly happy to announce this release, since it is 💯 % brought to you by contributors!
I'd really like to 👏 and 🙏 and 🎉 those really nice people for these...
Kernel#open to using File#Open (tech ref. here)wordmove pull -d -e productio anyone? - now you'll receive a really clear and polite error message instead of an exception with an ununderstandable error--path flag passed to wp-cli now has super powers! Wordmove will read it from your wp-cli.yml when present, otherwise it will set it to its own wordpress_path. This will enable you to easily manage exhotic scaffolds or practices. Any Bedrock user out there? Read more about the discussed features @ #590 and #591. And I'm really happy to thank @nlemoine too, for his terrific report and his contribution to the discussion. The documentation is updated to inform about the behaviour: https://github.com/welaika/wordmove/wiki/movefile.yml-configurations-explained#global-options
I'm totally thrilled by this participation ❤️
A hug 🤗 to all the community hard facing up to COVID-19 👾 . Be safe and keep it up. 💪
The new hook data structure introduced in https://github.com/welaika/wordmove/releases/tag/v5.0.0 was implemented with a main goal: having an arbitrary order on hooks. Due to a bug the code was anyway grouping the hooks by local/remote before the execution, thus breaking the expectation.
Full commit history @ https://github.com/welaika/wordmove/compare/v4.0.1...v5.0.0
New major version, so prepare for the...
hooks has changed it's data structure. Reference to https://github.com/welaika/wordmove/pull/557 and linked issue for the history. All the documentation has been updated, so let's take a look there. Documentation for older version retained in the dedicated wiki page https://github.com/welaika/wordmove/wiki/Hooks
list command enters the show! https://github.com/welaika/wordmove/pull/548 All of us have to thank @akiko-pusu for the excellent work! 👏:database, :password
:database, :host
:vhost
:ssh, :password
:ssh, :host
:ftp, :password
:ftp, :host
:wordpress_path
wpcli adapter even if you're working outside the project directory. More @ https://github.com/welaika/wordmove/pull/513 and all the applauses go to @tnzk 🎉 👏Using Movefile: xyz should be fixedWith the help of @huraji we have discovered a voodoo-ish trick about how to push/pull only specific plugins and themes. If you're curious we have produced a little wiki page @ https://github.com/welaika/wordmove/wiki/Work-only-on-specific-plugins-or-themes 👏
That's all folks 🐰
Thanks to @laposlaszlo and @nghh on issue #506 to have spotted this out
Unfortunately this is a major version w/o a lot fun inside :) Anyway I thought about it and IMHO worth the major bump in order to raise your attention about why this release could break something.
The only and interested commit is
Follow the commit link to read full (?) explanation. But here it is the short one: if you relied on hooks chain in your movefile.yml having a hook exiting with error (a failing hook) before Wordmove just logged the fact and continued its work while now Wordmove logs the fact and exists throwing an exception (so w/ a non-zero exit code).
So as far as it is formally a backward compatible new behavior, we can't risk to let you update production environments or CI/CD servers without a little warning and attention.
The change is introduced because:
a must be completed successfully in order to run b; before it was not possible)a && b && c into single, more readable hooks - 'a'
- 'b'
- 'c'
obtaining the same behavior as using bash's && operator.
My advice is to wrap your maybe-fail hooks in little shell scripts and manage from there the return status (explicitly exit 0 at the bottom would be enough in most cases)
Full what changed report at https://github.com/welaika/wordmove/compare/v3.2.2...v3.2.3
Resume:
bundler you just need to update it one-time with gem install bundler
In the meantime me and all the developers at weLaika would love to