- Linode 512 MB
- Debian 6 32-bit
- APC (for opcode and object cache)
- WordPress Multisite
I documented my setup and after testing it with another friend (it worked!) and mentioning it to a couple others, decided to post it here. I’m going to assume you’re familiar with the basics of administering a VPS, especially SSH.
I did this on Linode, but it will probably work fine on pretty much any VPS (or dedicated server). It won’t work on a shared host because it depends on installing specific software that requires root access. My server needs are not very extravagant so I chose Linode’s cheapest plan, a 512 MB VPS. You’ll need to choose a location for your server, and since I have no idea what the practical differences are, I went with Dallas based on a recommendation. For the purposes of this tutorial, it doesn’t matter which one you choose.
Go through the Linode setup, choose the Debian 6 32-bit distribution, get your ssh information, and login to your new server. If you use a larger VPS you might want the 64-bit distribution, but on a 512 MB server that’s going to cause problems.
Linode has a very good tutorial on the first few things you’ll want to setup with your new Linux install. Once you’re logged in you can skip to the security section in Linode’s “Getting Started” tutorial. That will walk you through:
- Updating your package installer
- Setting your server’s hostname
- Setting the timezone
Your settings here can be unique to you. In my case I like to name computing devices after Yankees players (see my external hard drive named Mattingly) so I called my Linode server
dimaggio. I like to use my local time, which is
America/Los_Angeles in the Linux world. Some people like to use UTC, which we do at Automattic. Pick your poison.
Before you go any further, you should install
sudo because you’ll need it soon and your server won’t have it by default. You can do it with this one liner:
apt-get install sudo
Now that you have the basics setup, it’s time to move onto the real stuff — users, permissions, firewalls, and software. Slicehost has two great tutorials on this: Debian part 1, and Debian part 2. We’ll go through these now.
You don’t want to be logged in as
root any longer than you absolutely have to. The first thing Slicehost will walk you through doing is creating a new user account. They use the username
demo but you’ll probably want to use your first name. In my case I skipped the additional group management steps; I don’t plan on managing a large number of users and it’s easier to have fewer moving parts. If you don’t assign your user to a group, it will be automatically put in a group with its own name — my user is in a group called
evan. Slicehost will walk you through the details, but I’ll add one suggestion: do not log out of your root SSH session until you’ve successfully logged into your user account and confirmed that your
sudo access works. Otherwise you’ll need to reset your whole server and start from the beginning. Once you’re setup, move onto part 2.
Part 2 mainly covers Bash and the Aptitude package installer. I am pretty particular about my bash prompt. You can grab the key parts of mine here. This does a few things:
- Shorten long directory names by replacing the middle with an ellipse
- Add the git branch name to the prompt (if you’re in a git repo)
- Use up and down arrows to search your bash history using whatever you’ve already entered as a search prefix
- Make tab cycle through available commands instead of listing them
- Add tab-completion for git commands
The git pieces rely on this git auto-complete script.
Once you’ve got your
.bashrc setup and your package repositories updated, it’s time to move onto the the next step: PHP-FPM.
The stack: PHP-FPM
Debian’s default package repository has an outdated version of PHP-FPM, so first we’re going to add a new repository to our list. Aptitude’s repository list is kept in
/etc/apt/sources.list and we want to add a new line with this repo:
deb http://packages.dotdeb.org stable all. You’ll need to use
sudo to edit this file and save it. When you’re finished, it should look something like this. Now go back to your home directory and setup your new repository.
cd ~ wget http://www.dotdeb.org/dotdeb.gpg cat dotdeb.gpg | sudo apt-key add - rm dotdeb.gpg sudo apt-get update sudo apt-get upgrade
Now we can install PHP and its siblings:
sudo apt-get install php5 php5-fpm php-pear php5-common php5-mcrypt php5-mysql php5-cli php5-gd php5-apc
We’ll be using PHP-FPM to handle all of the PHP requests that come in through nginx. To do that, we’ll need to update the PHP-FPM config at
/etc/php5/fpm/pool.d/www.conf. We will set PHP-FPM to decide how many processes it will run and how it will listen for requests from nginx. My config file is here. It will set PHP-FPM to spawn a reasonable number of children and servers for 512 MB VPS and configure it to listen over a Unix socket instead of a TCP port. These settings may not be perfect for you, but they should get you started.
Restart PHP to make sure your new settings are in effect.
sudo /etc/init.d/php5-fpm restart
The stack: nginx
We’re going to use nginx as our web server, so first we’ll install it.
sudo apt-get install nginx
Now we’ll setup our nginx config at
/etc/nginx/nginx.conf to tell nginx how to serve our data. This file is pretty straightforward, but it does assume you’re using the 512 Linode server (or another one like it). You can grab mine here.
Once you have your config in place, restart nginx to use the new settings.
sudo /etc/init.d/nginx restart
The stack: MySQL
The last part of your stack is MySQL, which we will install now:
sudo apt-get install mysql-server php5-mysql
Once you complete the MySQL installer you can head over to Linode’s low memory settings tutorial to configure some settings for MySQL geared toward low memory servers (which a 512 MB VPS is). I followed their guidelines in my config, so I won’t copy it here. The last two items won’t be in your default my.cnf file, so you can add them at the bottom.
One last thing you’ll want to install here, even though it’s not a part of the traditional L(A|E)MP stack, is an email server. Again, Linode has a great send-only mail server tutorial. If you want to configure a mail server to actually receive email, that’s outside the scope of this post. In my case my server’s only interaction with mail is to send it — for example, when you need to reset your WordPress password.
There are lots of ways to get WordPress installed. In my case, I had a few requirements that guided my choices:
- I’m using WordPress multisite
- I’m using the multisite domain mapping plugin
- WordPress will manage my whole site
- My site will be version controlled with git
After experimenting with lots of different options, I decided on this setup:
- My public directory will just be a copy of my git repository
- WordPress will be installed in my git repository as an
- Local development will use Mark Jaquith’s local config setup
At this point, you’ll want to install git on your server so that you can pull in your repository. Again, a one-liner will do it for you:
sudo apt-get install git-core
I setup my git repository and exported WordPress trunk, then setup my
local-config.php per Mark’s instructions. Next I setup my
.gitignore file to make sure I didn’t accidentally commit any of the local-specific data.
.DS_Store /local-config.php /.htaccess /wp-content/uploads/ /wp-content/blogs.dir/ /wp-content/plugins/hello.php
I won’t walk through the WordPress multisite installation. If you need help with that, there’s a great Codex article that covers it. The only part specific to this tutorial is that you won’t want to use the
.htaccess file (notice how I
.gitignore‘d it?) because we aren’t using Apache. Instead, you’ll use a nginx config file to handle this. In my case, I put a file called
.nginx-config into the root of my git repo and symlink it to nginx’s
sites-enabled directory. You can grab my config file here — obviously you’ll want to replace domain.com with your actual domain. I have a couple other rewrite rules specific to my site, but this should cover the basics.
Again, that config goes into your git repo, which means nginx has no idea it exists yet. Once you’ve pulled your git repo onto your server, you can symlink it to the place nginx will look (
/etc/nginx/sites-enabled). In my case my web sites are being served from
/srv/www/domain.com/public, so that’s where my git repo will be pulled. This directory won’t exist by default, so you’ll need to create it as well as
/srv/www/domain.com/log, which is where nginx will store your access and error logs. You can put your website content in another directory if you want, but you’ll need to change the nginx config file to make it work. Now you can symlink your config by running:
sudo ln -s /srv/www/domain.com/public/.nginx-conf /etc/nginx/sites-enabled/domain.com
This will take care of copying your rules to nginx, and it will also block nginx from serving that file publicly because it starts with a dot.
Restart nginx to make sure it uses your new virtual host.
sudo /etc/init.d/nginx restart
Last, you’ll want to setup caching for WordPress. I’m using Batcache, which uses the WordPress object cache for all of its page caching. We use it on WordPress.com and it’s super-configurable, but I’m using it with the out-of-the-box settings for now. Batcache requires a persistent object cache backend, which Mark Jaquith’s APC plugin is perfect for on a one-server setup. If you’re running multiple servers you should use Ryan’s Memcached plugin (and you should also have stopped reading this a while ago). We already installed php5-apc (along with the rest of PHP) so there’s no server config needed here.
The Batcache installation is pretty straightforward. You will put Batcache’s
/wp-content/mu-plugins (which you’ll probably need to create). Then you’ll put Batcache’s
/wp-content. Finally, you’ll put APC’s
/wp-content (the same place as
advanced-cache.php). You’re almost there, you just need one line in your
wp-config.php to tell WordPress to use the cache:
define( 'WP_CACHE', true );
That’s it. You should be good to go with a very fast and easy (relatively speaking) WordPress setup. There is some other house keeping you might want to do, like hardening WordPress, but I’ll skip that for now because there is plenty of good information about it on the Codex. You’ll also need to setup your DNS, both within Linode and in your domain registrar. This is no different than any other setup so I’ll skip that as well. Finally, you may want to configure other server-specific settings, like rotating logs. You should check out Linode’s tutorials on those.
For a bit of fun, you can run Apache’s benchmark test to see how many requests your server can (in theory) serve per second. First you’ll want to install Apache’s dev tools. Once you do that, from your server, we can throw a bunch of traffic at WordPress:
sudo apt-get install apache2-dev ab -n 10000 -c 1000 -H 'Host: domain.com' http://127.0.0.1/
The output will include a “Requests per second” line, and in my experience you should be able to hit the mid-6000’s.
Edit: I really do want to clarify this is mostly for fun, and not a useful metric of how much traffic you’ll be able to handle. The one place this is actually useful is comparing your new server to an old server, purely on a relative basis. For example, my old site running Apache with
mod_php came in around 200-300 requests per second. So I can get a sense of how much faster the new server is, but it does not mean I’ll be able to serve 500m page views per day from one VPS.