Wordpress Multisite WPMU + Nginx blog into subdirectory

Forums › IT Pro and developers › Wordpress Multisite WPMU + Nginx blog into subdirectory

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#189524 3-Jan-2016 08:41

I'm migrating all my blogs (four of them) into one folder on a VPS (AWS) using Nginx as the web server. Three of the blogs have wordpress run the entire domain, one has custom PHP application on the site root with Wordpress in the blog subdirectory.

WPMU (Wordpress Multisite) seems to only support putting the install onto the root of the domain. I'd prefer to keep it in the blog directory, where it is now. Does anyone have any clever ideas how to either get it into the blog subdirectory, or make it appear like it's in there? Something fancy with Nginx? Maybe put the blog into a subdomain and map it to a folder of the main domain? I don't want it to run on the subdomain as it has SEO implications.

I know I could run a standalone Wordpress install, that's my backup plan.

nunz

1421 posts

Uber Geek
+1 received by user: 314
Inactive user

#1477676 24-Jan-2016 09:40

There are a lot of indicators that wordpress multi is more difficult to manage than multiple wordpress sites. I personally keep one wordpress install per site.

That would also solve your /blog issue.

Under linux.,...

Say my code folder looks like:

/-var/www/Site1

|-Site2

|-Site3

|-Blog

and i want the blog under site1 as site1/blog

then

cd /var/www/Site1

ln -s /var/www/Blog

will make a link to the blog, under site1 which will be indistinguishable to

/-var/www/Site1/Blog

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#1477678 24-Jan-2016 09:45

I ended up deciding that what I wanted was impossible, so I did a single site install of Wordpress for that site. I have three other sites where Wordpress runs the whole domain, Wordpress Multisite runs all of those fine. Yes it's a bit more difficult to set up and manage, but it's fine. I'll be putting it all into production soon, if I have any trouble I'll switch back to single site.

One reason I did it is because it seems more efficient to have one install, especially using HHVM (PHP running in a JIT), so it can optimise Wordpress once rather than a bunch of times. Just saves a tiny bit of disk space I imagine. The main reason was ease of management - one install to maintain - well two now.

I'm just in the middle of moving my AWS sites to a US region from Sydney, as my key websites key customers are in the USA.