WordPress Development Stack Exchange is a question and answer site for WordPress developers and 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

Update: I came by a reasonable alternative to the approach explained below, instead using a GIT repo and a WordPress Multisite plugin: Deploymint: a staging and deployment system for WordPress.


We have created a separate folder on our server, like /root/sitetest/wwworg/, for the test.jmonkeyengine.org sub-domain (not multisite, just a custom created sub-domain).

We've also set up Webmin on the dedicated server hosting our sites. One of our developers has constructed a really handy script in Webmin's "Custom Commands"; at the click of a button an exact copy is made of our live site and moved over to test.jmonkeyengine.org where we can play around in a live environment at no risk.

We'd like to enable WordPress Network, but it seems very likely that doing so would make it difficult, if not impossible, to maintain this method of site testing.

I'm not a very technical guy, but I'm seeing two possible options:

  1. We do a sub-directory install. This should hopefully enable the cloning script to go about its business as usual, as there's no tricky domain changes involved. If we still wanted to apply sub-domains, I suppose maybe we could still do that by using the MU Domain Mapping plugin, or by setting up our own masks(?). I don't know how well that would go over with various SEO plugins though, e.g. analytics & sitemaps. Furthermore, our site is not "new", which apparently is required in order to make a sub-directory install possible.
  2. We do a sub-domain install (preferred). However instead of reassembling the cloned sites on test.jmonkeyengine.org (I assume we couldn't easily copy jobs.jmonkeyengine.org to jobs.test.jmonkeyengine.org) we'd point it to some new top level domain like jmonkeytest.org, that could handle sub-domains. Maybe some changes would have to be made in .htaccess and so forth either in the script or by hand. Whether or not it'd be worth the otherwise convenient test setup remains to be seen.

Does anyone have any experience with this type of setup?

share|improve this question

closed as not constructive by toscho Jul 12 '12 at 22:52

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Are you talking about making your production sites network enabled to host your test sites under them? – Dave Konopka Jul 12 '11 at 5:21
Hey, sorry my reply took so long, I was expecting e-mail notifications. No, that is not what I meant. Here's what I'm talking about: We are currently using the test sub-domains to host our test sites. That works great so long as we aren't using sub-domains for the rest of our sites. However, what if we enable Network and establish jobs.jmonkeyengine.org, wiki.jmonkeyengine.org and showcase.jmonkeyengine.org. I strongly doubt the simple transfer to test.jmonkeyengine.org could work the same way from now on. I'll try clarify the head post, thanks. – Erlend Jul 16 '11 at 6:52
I came by a reasonable alternative to this approach, using a GIT repo and a WordPress Multisite plugin: markmaunder.com/2011/08/19/… – Erlend Aug 25 '11 at 2:53