KUSANAGI Update 8.4.2-2

KUSANAGI Update 8.4.2-2

KUSANAGI8.4.2-2 update has been released.

– If a database name or user name including “-” exists in KUSANAGI, it can not create a database name or user name without “-” starting with the same name.

– When the English version of WordPress is installed, added or updated plug-ins and theme translation files are not applied.

To enable the aforementioned features, execute the following command as root user:

# yum update

KUSANAGI Module Update

The individual modules that makeup KUSANAGI have been updated.
The updated module versions are as follows:

 

nginx 1.15.9
php7 7.3.3
OpenSSL 1.1.1b

The module update can be applied with the following command:

# yum update

KUSANAGI for GCP is now available

KUSANAGI for GCP is now available.

Please see the guide at KUSANAGI for GCP

Simply Fast WordPress [16] – Enabling Always-On SSL and HTTP/2 on an existing HTTP WordPress site (Part 2: Application)

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. This time, we will explain step-by-step how to implement Always-On SSL and HTTP/2 on an existing HTTP WordPress site.

Last time, as preparation for enabling HTTP/2 and Always-On SSL, we explained how to migrate an existing WordPress site over to KUSANAGI. This time, we will show how to enable HTTP/2 and Always-On SSL on sites already running on KUSANAGI.

If you just started reading this blog from this article or you have a WordPress site that is not running on KUSANAGI, please read the back issue “Enabling Always-On SSL and HTTP/2 on an existing HTTP WordPress site (Part 1: Preparation)” and follow the instructions from step 1.

Simply Fast WordPress [15] – Enabling Always-On SSL and HTTP/2 on an existing HTTP WordPress site (Part 1: Preparation)

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. This time, we will explain how to implement Always-On SSL and HTTP/2 on an existing HTTP WordPress site.

Last time, we explained how to set up a new WordPress site that uses Always-On SSL and HTTP/2, first with free certificates through Let’s Encrypt in Vol 13, then with business SSL certificates in Vol 14.

However, there are probably many of you who already have your own WordPress site running. Over the next two installments, we will explain how to migrate existing HTTP WordPress sites to KUSANAGI and configure them with Always-On SSL and HTTP/2.

Along with this article, please check “Using KUSANAGI – Adding Always-On SSL and HTTP/2” for some basics on Always-On SSL and HTTP/2 and why they are necessary.

Simply Fast WordPress [14] – Using KUSANAGI – Adding Always-On SSL and HTTP/2 (Part 2. SSL Server Certificates for Business)

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. This time, we will explain how to install Always-On SSL with SSL server certificates for business, and HTTP/2.

Last time, we explained how to install Always-On SSL and HTTP/2 using free SSL certificates from Let’s Encrypt.

This time, we will explain the significance of using SSL server certificates for business-use from services like Digicert, Globalsign, Network solutions, and Symantec. We will also explain how to install them along with HTTP/2. In this article, we assume that you have provisioned WordPress with KUSANAGI, so it is recommended that you read “Using KUSANAGI – Adding Always-On SSL and HTTP2 (Part 1. Let’s Encrypt)” first.

Simply Fast WordPress [13] – Using KUSANAGI – Adding Always-On SSL and HTTP2 (Part 1. Let’s Encrypt)

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. This time, we will add support for Always-On SSL and HTTP/2 to our WordPress site, and explain how to get a free SSL certificate from Let’s Encrypt.

In the last issue, we verified how fast KUSANAGI, the “1000x speed tuned” virtual machine for WordPress, really is.
In this practical guide, we will enable Always-On SSL and the high-speed transfer protocol HTTP/2 on a WordPress site. We will also explain how to get a free SSL certificate from Let’s Encrypt.

Simply Fast WordPress [12] – How fast is KUSANAGI, the “1000x speed” WordPress virtual machine?

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. In his article, we will verify just how fast KUSANAGI is when operated on a public cloud.

Last time, we introduced seven merits of running a KUSANAGI, the WordPress 1000x speed-tuning virtual machine.
This time, we will launch KUSANAGI on a public cloud service, and verify its speed. We will use KUSANAGI for AWS (Amazon Web Services) and compare the results to the results from our speed-tuning efforts in articles 2-10.

Simply Fast WordPress [11] – What is KUSANAGI, the “instantly 1000x faster” speed-tuned WordPress virtual machine?

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. --Kengyu Nakamura, Prime Strategy Co., Ltd.

In this article, we will introduce seven merits of using KUSANAGI, the speed-tuned virtual machine that achieves 1000x speed right away, without carrying out each individual tuning technique explained in previous articles.

Using these techniques, we increased WordPress’s requests per second from 11.24 (using the default LAMP – Linux, Apache, MySQL and PHP) to 205.2 (using Nginx and HHVM 3.15) to 12672.3 (with Nginx’s FastCGI page cache). In other words, we are able to speed up WordPress to 1127x its speed in the default environment. If you are using WordPress for business, there is no reason not to put these techniques to use.

KUSANAGI module update

The modules that composed KUSANAGI had been updated. The new versions are as follows.

NGINX 1.11.5

Use the following command to update modules.

# yum update