WPCD Multi-tenant supports a distributed multi-server environment including:
However, this environment requires a bit more configuration setup than one where template & customer (tenant) sites live on the same server.
If you have multiple templates, you can divide them up among multiple servers. This is useful if you create a lot of versions and you have multiple templates. You can then split those templates across different servers.
There is no special configuration required for this – just initialize your template site as usual on any server.
If you need to to move a template from an existing template server to a new one it is a multi-step process:
In the most basic WPCD Multi-tenant configuration, template sites (with their associated versions) and tenant sites live on the same server. But, you can create new tenant servers so that you do not have all your eggs in one basket.
On each new tenant server you will need to seed it with the version sites and related version files. To do this:
For Each Template:
So, if a template has 5 versions (this means 5 version sites), you will use the COPY TO SERVER function on each version to get them to the new tenant server. In many cases you can choose to copy only the latest PRODUCTION version since that’s the one most likely to be used for new tenants.
It is not necessary to copy the template itself to the new tenant server. Only the version sites need to be copied along with the version files (the 2nd bullet point above).
With multiple tenant servers, creating new versions require an extra step.
Every time you create a new version that will be used for tenant (customer) sites, you need to repeat the steps above to ensure that each customer (tenant) server has all the files needed to create new tenants and upgrade existing ones.