Multi-stage command line deploy/mirroring and task runner for Wordpress
MIT License
Bot releases are hidden (Show)
mu-plugins
. Now it is fixed (thanks to @seanclen)Published by alessandro-fazzi almost 4 years ago
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.
Published by alessandro-fazzi over 4 years ago
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. 💪
Published by alessandro-fazzi almost 5 years ago
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.
Published by alessandro-fazzi almost 5 years ago
Published by alessandro-fazzi almost 5 years ago
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 🐰
Published by alessandro-fazzi over 5 years ago
Thanks to @laposlaszlo and @nghh on issue #506 to have spotted this out
Published by alessandro-fazzi almost 6 years ago
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)
Published by alessandro-fazzi almost 6 years ago
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
Published by alessandro-fazzi about 6 years ago
Published by alessandro-fazzi about 6 years ago
With https://github.com/welaika/photocopier/releases/tag/v1.3.0 we now fully support SFTP protocol in Wordmove. Thanks @xwulfus for his hard testing! We think SFTP is a better place and option over FTP, so we decided to give some love to people who are bound to this protocol.
Hope you'll enjoy
Published by alessandro-fazzi over 6 years ago
With this release we're fixing #479 and #480. The former is particularly interesting for all the bedrock's users 😃
Thanks to @matthewnw, @akishin and @maiorano84 for their contribute. ❤️
Published by alessandro-fazzi over 6 years ago
and...well... 😰
Had some problem setting up the docker auto-trigger on travis. Not cleaned the history as a reminder of this tragic moment.
Published by alessandro-fazzi over 6 years ago
Thanks @rbndelrio for his awesome contribute in #469 !!! Go there and read or go in the main readme and search the new "Secrets" section! 🎉
Thanks @dompl to have reported a bug born with wordmove and - hopefully - fixed just now. Fixing #428 required an update to welaika/photocopier and a little revolution in how we make rsync work behind the scenes. We'll keep a close eye on this new behaviour in order to catch regressions ASAP.
Help in debugging always welcome! 🎁
Published by alessandro-fazzi over 6 years ago
So it's important to read release notes ;)
charset
option, add mysql_optionsNow you will need wp-cli
installed by default. You can always change back to the default
adapter, but you should go ahead and install wp-cli
as a better choice!
We have dropped the database.charset
configuration, and we have updated docs in the wiki with suggestions to preserve the previous behaviour.
Hooks, our previous new shiny feature, got improved: remote hooks will be run by default inside the remote wordpress' directory. So you won't have to manually cd
in your commands. We hope you'll appreciate. And obviously related documentation is up to date in the wiki ;)
🎉 🎉 🎉 🎉 🎉 🎉
#205 and #447 are closed feature requests now! We really hope this feature could be useful for the community, since we have implemented it "just" for you :P
charset
option, add mysql_optionsNow you have both database.mysqldump_options
and the new database.mysql_options
available in the movefile.yml
. Ref: #460 and #463 and thanks a lot to @sag5515. This is another step towards a better support for docker environments. (Psss: have you noticed https://github.com/welaika/docker-wordmove ???)
This means that you can pass options to both mysqldump
command, used for db export, and mysql
command, used for db import.
Let us know if you're happy at https://twitter.com/weLaika
Published by alessandro-fazzi over 6 years ago
This should be useful to use wpcli inside docker environments where root
is the default user
Published by alessandro-fazzi over 6 years ago
Doctor improvements:
Published by alessandro-fazzi over 6 years ago
doctor
movefile validator accepts https
protocol in local.vhost
key.
Published by alessandro-fazzi over 6 years ago
doctor
was not not able to test when custom port was used.
Also improved code with shell escaping and using right access to config
hash (by symbol now)
Published by alessandro-fazzi over 6 years ago