Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are having wordpress multi-site and the developers do there development on dev server, We are not using any version control for wordpress development, I need some plan so we can move the site from dev to live fast and secure.

I was thinking about inotify + rsync but what about the db promotion?


locked by HopelessN00b Jan 21 '15 at 8:10

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off-topic by HopelessN00b Jan 21 '15 at 8:10

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 2 down vote accepted

Actually we do wordpress multisite development in and then need to move to live site which is, so we need to change all the links in the files and db both from to and move the mysql from dev server to the live. Currently I am doing that manually but now I found wordpress plugin named duplicator, that works for me including the links changes and mysql export/import etc.

More detailed answer and other plugins look for the following question.

Thanks for sharing your knowledge and research. There are apparently many ways to solve this problem. :) – Michael Hampton Sep 11 '12 at 8:17

WordPress has a simple 503 "maintenance" page which you can (and should) enable during a code deployment. If you upgrade WordPress from within itself, then it enables and disables this page automatically.

If you want to enable it yourself, simply create a blank file .maintenance in the top level WordPress directory, and delete it when the deployment is complete.


touch /srv/www/
rsync /srv/www/
# custom scripts here, if any
rm /srv/www/

At this time, a WordPress user with the Administrator role must now visit (for multi-site; remove /network for a single site) to update the database schema. I don't know of any good way to do that offline; however WordPress is pretty good at continuing to work with an out-of-date schema.

Thanks Michael but the answer I was looking for I found on the wordpress forum I answered my own question if you can verify that. – Toqeer Sep 11 '12 at 8:12

Not the answer you're looking for? Browse other questions tagged or ask your own question.