More than one person has asked me for my Nginx Virtual Host recipe for WordPress Multi-User and BuddyPress, so I’m posting it here. The attached virtual host definition is feature complete and works for me on a number of production sites.
Be sure to change domain.tld to your actual domain name. The wildcard record will allow your site to respond to ANY sudomain request, which may not be something you want.
You’ll also need to change the path to your log files, as well as the path to your public webroot folder. Finally, up the client_max_body_size to match your upload_max_filesize and post_max_size settings in php.ini.
Finally, this assumes you are running your PHP fast cgi process on port 9000.
This is the recipe for WordPress MU / BuddyPress. I’ve also posted one for WordPress (single site) and Drupal.
Download Nginx vhost Recipe for WordPress Mu and BuddyPress
Please post ways to improve this in the comments. I use this on a number of production sites, but there is always more one can do. Thanks to all of the blogs and articles that I ripped off helped me understand Nginx and got me started.
Since more than one person has asked me for my Nginx Virtual Host recipe for WordPress sites, I’m posting it here. Be sure to change domain.tld to your actual domain name. The wildcard record will allow your site to respond to ANY sudomain request, which may not be something you want.
You’ll also need to change the path to your log files, as well as the path to your public webroot folder. Finally, up the client_max_body_size to match your upload_max_filesize and post_max_size settings in php.ini.
Finally, this assumes you are running your PHP fast cgi process on port 9000.
This is the recipe for WordPress (single site). I’ve also posted one for Drupal and WordPress MU / BuddyPress.
Download Nginx vhost Recipe for WordPress
Please post ways to improve this in the comments. I use this on a number of production sites, but there is always more one can do. Thanks to all of the blogs and articles that I ripped off helped me understand Nginx and got me started.
Or how to create a blog network with out WordPress Multi-User.
Almost 2 years ago, I was charged with the duty of building an integrated Blog network with WordPress, for the Parents Everywhere Network. WordPress MU wasn’t quite ready for prime time, as most plugins hadn’t been ported over, and documentation was sparse, and only the bravest of souls wanted to tangle with it. Remember, this was back before WP and MU development were in sync. So I had to come up with another way.
Continue reading ‘Implementing the WordPress Shared Users Table Trick’
I started moving my open source code over to GitHub, since it supports working with contributors in a natural, but controlled manner. However, for many of my WordPress plugins I already have a local working copy, since they are hosted in the WordPress plugin repository to support auto-update. I didn’t want to disrupt my svn working copy, nor did I want to start fresh in github.
Continue reading ‘One working copy to rule them all (Git + SVN)’
If you get errors like: configure: WARNING: unrecognized options: --enable-apc when statically compiling PECL modules, such as APC into PHP, then ensure you have the proper version of autoconf installed (version 2.13). On Ubuntu that was fixed with a quick sudo apt-get install autoconf2.13
Then you can get back to removing your configure file and running ./buildconf --force before you re-compile.
comments