After exploring WordPress-Nginx Configurations for standard/single-site setup, its time to explore WordPress-Nginx Configuration for Multisite setup.
In today’s article, we will take a general overview of WordPress-Multisite. Then in the subsequent chapters we will explore different Nginx configurations.
There are three ways in which WordPress Multisite can be configured. Each has its own use cases and different level of setup complexity.
|Configuration||Sub-directory mode||Sub-domain mode||Sub-domain with Domain Mapping|
|Site Address Examples||example.com/site1|
|DNS requirement||None||Wildcard domain name support||Wildcard domain name support|
|Ongoing DNS Efforts||None||None||Creation of “A” or “CNAME” record for “mapped” domains|
|Dedicated IP||Not Required||Not Required||Required – if we want to use A-records for “mapped” domains|
|Common Usage||Development environment, Demo Sites||Blog Networks with generally common owner, Community Sites||Open Blog Networks, WordPress as CMS hosting|
* Note: In domain mapping mode, its not compulsory to map top level domain for every site in Multisite.
There are some differences and quirks you need to be familiar when running a WordPress-Multisite network. All of these will be addressed in separate chapters for three modes.
If you have never used WordPress Multisite before, its better to check right now if it is a good choice going ahead. We get this question many times from our clients.
Is WordPress multisite right choice?
WordPress multisite has many advantages but in some cases you may regret going for it. For this reason I am addressing this question earlier and quickly.
WordPress-Multisite may prove bad:
- If there is remarkable difference between functionality of sites. For example, if you put mixture sites running e-commerce, event-website, membership portal, bbPress-forums, job-boards, community blogs, big CMS, wikis, etc – you will end-up with complicated user-permissions which you will find hard to manage. There are some plugins to help you out but from management perspective you will have hard-time.
- As you host hybrid sites, total number of plugins will keep going up. You can activate/deactivate plugins per site, but then again managing plugins will get tough. Also, if plugins you uninstall leaves a database tables behind, your WordPress database will become bloated soon.
- One poorly coded theme/plugin can bring an entire network down. I see people using poorly coded/outdated plugins in Multisite. They think a bad plugin may impact just 1 site but most likely it will degrade the performance of the entire network.
Good things about WordPress-Multisite:
- Multisite works very well when you have similar sites in network. For example, wordpress.com itself. They offer some paid-feature but list of plugins/themes they maintain is same across all sites.
- It has some administrative advantages like ease of maintaining WordPress in terms of backup, upgrades, etc. But this can be done easily using other tools & scripts so this advantage alone is not worth going for WordPress Multisite.
Technically, Multisite comes with some performance issues out of the box, but these can be solved by small tweaks. In terms of scaliblity, you can again look at wordpress.com stats which is proof of WordPress Multisite scalability! So performance issue can be ignored if you are willing to put some efforts into tweaking.
Nginx itself is capable of handing many performance issues. I will shed more light on this in the next chapters.
You can also find the complete list of WordPress-Nginx tutorials here.