WordPress multi-tenant directory structure sharing core files for opcode awesomeness, fast deployments, and low disk usage. With inspiration from @weskoop. "=>" indicates a symlink.

gistfile1.txt

sites
  |__ ms.dev
  | |__ content
  | |__ index.php
  | |__ wp => ../../wordpress/stable
  | |__ wp-config.php
  |__ one.dev
  | |__ content
  | |__ index.php
  | |__ wp => ../../wordpress/stable
  | |__ wp-config.php
  |__ two.dev
  | |__ content
  | |__ index.php
  | |__ wp => ../../wordpress/stable
  | |__ wp-config.php
wordpress
  |__ 3.5.2
  |__ 3.6
  |__ stable => 3.6
  |__ wp-config.php

@troychaplin79 — Cheers!

@troychaplin79 How can I get in touch with you regarding multitenancy work?
Thanks

@troychaplin79 How can I get in touch with you regarding multitenancy work?
Thanks

My contact info is in my git profile

@troychaplin79 How can i setup your wp-multitenant plugin on my cPanel hosted website is their any specific way for that.

@troychaplin79 How can i setup your wp-multitenant plugin on my cPanel hosted website is their any specific way for that.

sorry for the late reply @waqassalman, I've been reworking several aspects of my wp-multitenant repo which also includes an improved readme, the recent changes can be found on the develop branch at the moment. To set this up you'll need access and some knowledge of working on your server via SSH.

I really like this concept of wp-multitenant, will this setup works on the existing setup of WordPress installed on docker?