• Mestika

    (@mestika)


    I’m searching for a solution to an architectural problem with an WordPress application I’ve made (please not that this question also has been posted on stackexchange)

    Each instance of the application is running on it’s own subdomain (a folder on root) and right now, each of these instances have a complete copy of WordPress, the theme and the plugins, and of cause their own database.

    My dream scenario is, that each subdomain instance share WordPress, the theme files and plugins. The uploads and database (namely posts and users) are not shared and must never be “mixed” so a user on subdomain instance #1 cannot log in or access anything on instance #2.

    Image of structure

    I’ve investigated multisites but that’s not the perfect solution in that the multisite is designed to share users across network and I really need to make sure security and seperation between users on different subdomains.

    Another solution, which is more a better-than-nothing solution is to define the content folders for each subdomain to be the same in root (WP_CONTENT_DIR & WP_CONTENT_URL) and then defined uploads to be within each subdomain folder. This make it easy to upgrade the theme and plugins but I still have the hurdle of updating all subdomains WordPress installations. But as said, better than nothing.

    Yet another way to go that I’ve examined is multi tenancy for WordPress. But unfortunately I’ve not access to SSH or to the system (Unix) or webserver (nginx) and I cannot get access (it’s on a web-host) and as far as I can tell this is needed to make a multi tenancy installation to share (perhaps via symbolic link) WordPress and content.

    Is there any other way to accomplish this structure or is my best chance to kick out my host and just buy a server (space) and manage the installation myself, including SSH and make it multi-tenant?

Viewing 1 replies (of 1 total)
  • Digico Paris

    (@digico-paris)

    Hello,

    I guess you could use Nginx proxy mode to push one part of solution (as Nginx hub). Though, you could have tables for each subdomain on same MySQL “group” (with different users – depends expected traffic).

    Also, for second idea, I fear it would be very counter-productive because of problems with automatic updates, and so on, like you mention.

    Anyways, both look like it would require a lot of setup and custom code time.

    My 2 cents conclusion, yes it’s better to go on a full VPS with full root admin rights. That will not only allow you better flexibility, but better control & insight on the whole project. (and nowadays it’s not hugely expensive to grab a nice VPS – some are a couple bucks per month).

Viewing 1 replies (of 1 total)
  • The topic ‘Multiple wordpress installations that shares WordPress & Theme but with separate’ is closed to new replies.