This year, I really wanted to work on my output, and I think I’m doing pretty well. Here are some things that I’ve been publishing:
Regular monthly blog posts on yakushima.blog A few posts this year on the Geolonia blog for work However, updates on this personal blog has been not so great – the previous post is the “2023 review” post, after all.
I’ve been updating this blog from 2012, when we officially incorporated Flagship.
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.
Redirect all non-HTTPS traffic to the HTTPS server.
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.
Update 2014/4/17: This site now runs WordPress 3.9, which seems to be working fine with HHVM. Also, compatibility has improved, thanks to a patch in the WordPress core specifically for HHVM.
I recently posted about how I switched out PHP-FPM (PHP’s FastCGI pool) for HHVM. Today I’ll be talking more about the install process on the server, and using it to set up WordPress.
What is HHVM? This is usually what happens in a (successful) startup[footnote]Twitter is (in)famous for its use of Ruby on Rails, which eventually had to be re-written in Scala, a language that runs on the JVM.
I really like Sublime Text. Today, I like it even more. Thanks to a blog post by Uesugi Shu, this long-open bug regarding Japanese character input has a viable workaround!
The link is in Japanese; I’ve (roughly) translated the steps required to achieve the same result below:
Open the Sublime Text keymap file. This is at ~/Library/Application Support/Sublime Text 3/Packages/Default/Default (OSX).sublime-keymap -- Sublime Text 3 didn’t let me edit the file in-place, so I had to use a different text editor.
So, I’m making some changes to this blog. I’ll start with the first, which is most obvious. I’ve decided to change the theme I’ve been using for 2 years to Expound by Konstantin Kovshenin.
Second, which may (or may not) be so obvious. I’m running this site on NGINX ( blog post), but I’ve switched out PHP-FPM for Facebook’s HHVM. Based on my preliminary benchmarks, response time is around twice as fast, and throughput has increased ten-fold.
The ease of making a WordPress theme is both a blessing and a curse. It allows people to get started with programming relatively easy – most hosting providers have PHP / MySQL, and the majority have a WordPress quick-install. However, this easiness comes with a dangerous pitfall – it’s easy to do the wrong thing. The classic example of this is query_posts (hint: never use it).
Today, I’ll talk about wp_enqueue_script and wp_enqueue_style.
Rails Turbolinks is pretty cool, right? I thought it would be pretty cool to use it on WordPress, too.
There are probably a lot of bugs, and it probably doesn’t work well with JavaScript-heavy sites. I’ve included the jQuery compatibility layer, but it’s still not perfect. Use at your own risk.
To install, just search the WordPress plugin repository for “turbolinks”
Or, available for download here:
http://wordpress.org/plugins/wp-turbolinks/ Contributors welcome!!!
WordPress 3.7 was just released.
Although there are quite a few features in this release, I want to talk about what I feel is the most important feature: automatic updates.
It’s a fairly simple - when a new version of WordPress is released, your installation will be updated (almost) immediately. As of 3.7, these automatic updates are limited to minor maintenance releases to make sure they won’t break your theme or plugin.
I’ve been playing around with Vagrant recently. It really is a great tool for setting up development environments quickly and cleanly - no more local MySQL databases with 100 separate databases!
There are a few ways to solve this problem that many WordPress developers have:
Use WordPress Multisite mode. Regularly clean your databases up and delete old ones. Use a common WordPress install, switching themes. Use Vagrant. I’m going to be talking about the last option, Vagrant, in this blog post.
