Single codebase installation to handle multiple (separate) WP sites

  • Hi,

    What is the current best way to have a single codebase of WordPress on a server to serve multiple WP-sites?

    I’m familiar with WP-MU but it is not what I have in mind. The goal is to have totally separate installations with their own plugins and themes (and none of those can see each others plugins or content). And of course the main goal would be the ability to upgrade all the installations just with upgrading the one single shared WP core.

Viewing 2 replies - 1 through 2 (of 2 total)

  • I’d suggest either having totally separate installations, or just using WP-MU. Other solutions (like using hard links in Unix) I haven’t tried and wouldn’t recommend that you try. If you ended up upgrading all (or some) of the files in another WordPress installation, and not updating the database, you could easily break something. You might be able to find a service or code a plugin that does what you want, though; a little googling turned up ManageWP, for example.

    Thread Starter alive

    (@alive)

    I currently have totally separate installations, tens of them. And since they all share exactly the same core files it is very frustrating and time consuming task to update them all if my customers have forgotten to do so.

    ManageWP seems to be the solution to this direction, although it’s much more complex that I would need.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Single codebase installation to handle multiple (separate) WP sites’ is closed to new replies.