I recently gave a quick talk about how I use Nginx, HHVM, MariaDB with WordPress on this blog at the March WordPress Meetup in Tokyo. Here are the slides:
I’ve published a Vagrant template for the setup detailed in the slides.
I recently gave a quick talk about how I use Nginx, HHVM, MariaDB with WordPress on this blog at the March WordPress Meetup in Tokyo. Here are the slides:
I’ve published a Vagrant template for the setup detailed in the slides.
In my quest for faster response times and page load speed, I’ve been playing around with Google’s SPDY. I finally got around to getting a SSL certificate for this website and installing the latest version of the SPDY module for Nginx.
WordPress, alone, doesn’t really support SSL on all pages out of the box — here are some extra things you probably want to implement.
server {
listen 80;
server_name keita.blog;
return 301 https://keita.blog$request_uri;
}
server {
listen 443 ssl spdy;
...
add_header Strict-Transport-Security "max-age=31536000";
...
}
Using HSTS has the benefit of letting the user agent know that all requests should be using the HTTPS protocol for this domain. This is important because some WordPress plugins and/or themes will prefer to use HTTP, even though the connection is HTTPS. I had a problem with some AJAX functions and Jetpack’s Infinite Scroll.
(Optional) Install a HTTPS plugin. Not required, but it might help some problems with non-HTTPS content domains, et cetera.
Update 2014/4/24: I’ve updated the template to work with the latest HHVM 3.0+, and also squished some bugs.
I’ve been talking quite a bit about WordPress on HHVM recently, and it’s gotten a bit of attention, so I decided to open-source my Vagrant setup for running WordPress on HHVM.
I originally made this Vagrant setup to test HHVM on my local machine before deploying updates to the theme, plugins, etc.
Have fun, and please ping me if you have any problems!