Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Multiple environments explained
Wordmove assumes one of the environments will always be your development env. So:
Movefile's first section name (
local: vhost: "http://site.dev" wordpress_path: "/Users/me/Sites/site-local" database: name: "wordpress" user: "root" password: "root" host: "127.0.0.1"
That is your local dev env and the
local node is mandatory. Full stop.
Other nodes on the same level will declare remotes. Here we have 2 remotes declared:
local: vhost: "http://site.dev" wordpress_path: "/Users/me/Sites/site-local" database: ... test: vhost: "http://site.net" wordpress_path: "/dev/www/" database: ... exclude: ... ssh: ... live: vhost: "http://site.net" wordpress_path: "/site/www/" database: ... exclude: ... ssh: ...
Note that they have same indentation level as
When you pull/push you can specify a remote w/
-e flag if you have multiple remotes.
If you have just one remote it will be used by default, so you can omit
pull, the destination will always be
local; tell Wordmove the environment from where it should take the bits w/
wordmove pull -t -e live
will sync from
push, the destination will always be the requested remote; tell Wordmove the required destination environment w/
wordmove push -t -e test
will sync from
Note about push/pull db
When you pull a DB
Wordmove will dump a copy of your local DB before overwrite it. It will be in
When you push the DB to a remote
Wordmove will save a dump of the remote's DB the same way, naming it w/ the remote's name:
Thanks to @charmcat who shared her troubleshoot with us and suggested to write down this page