Category: devops

Categories
devops

WordPress on Linode

After using Heroku for a WordPress installation (here and here), Metatooth’s next WordPress installation is running on Linode. Metatooth had been using AWS and Heroku for cloud hosting, the economic conditions of the pandemic made for a budgetary decision. In addition, experiencing the impact of an AWS failure on a business dependent on compute availability, and a desire to not further enrich Jeff Bezos, led to this change.

It always pays to start at the beginning! The desired outcome was  Setting Up Multiple WordPress Sites with LXD Containers. The very helpful “Before You Begin” section on each Guide led all the way back to Getting Started with Linode. For this author, the key understanding came when reading A Beginner’s Guide to LXD. After a couple false starts, voila!

tgl@electra:~$ lxc list -c ns4t
+--------+---------+----------------------+-----------+
|  NAME  |  STATE  |         IPV4         |   TYPE    |
+--------+---------+----------------------+-----------+
| db     | RUNNING | 10.88.102.185 (eth0) | CONTAINER |
+--------+---------+----------------------+-----------+
| nginx1 | RUNNING | 10.88.102.96 (eth0)  | CONTAINER |
+--------+---------+----------------------+-----------+
| nginx2 | RUNNING | 10.88.102.112 (eth0) | CONTAINER |
+--------+---------+----------------------+-----------+
| proxy  | RUNNING | 10.88.102.42 (eth0)  | CONTAINER |
+--------+---------+----------------------+-----------+
tgl@electra:~$

The nginx1 container provides https://electra.growherbert.com and nginx2 provides https://growherbert.com.  One stumbling point was that the listen directive for each proxied nginx container must specify both “ssl” and “proxy_protocol”. For example:

ubuntu@proxy:~$ cat /etc/nginx/sites-available/electra.growherbert.com 
server {
	listen 80 proxy_protocol;
        listen [::]:80 proxy_protocol;

        server_name electra.growherbert.com;

        return 301 https://$host$request_uri;
}

server {
        listen 443 ssl proxy_protocol;
 
        server_name electra.growherbert.com;

        ssl_certificate /root/.acme.sh/growherbert.com/fullchain.cer;
        ssl_certificate_key /root/.acme.sh/growherbert.com/growherbert.com.key;

        location / {
                include /etc/nginx/proxy_params;

                proxy_pass http://nginx1.lxd;
        }

        real_ip_header proxy_protocol;
        set_real_ip_from 127.0.0.1;
}
ubuntu@proxy:~$

Lastly was the need to switch DNS providers in order to make use of acme.sh in the proxy container. There was even a helpful Guide for using this script —Secure a Website or Domain with Let’s Encrypt and acme.sh. Switching was easy using Linode’s Domain Manager.

What are you doing with LXD Containers? Tell us about it in the comments!

Categories
devops

Magento 2 on Heroku

Magento 2

Magento 2 on Heroku is what powers the metatooth.com online shop. This is a WordPress.org blog running on Heroku. Look for a post on integrating the two in the future. My first step was to deploy to Heroku. Here’s one of the few resources I found, but it is a good one.

https://www.chrisgrice.com/blog/magento-on-heroku-part-1/

In a nutshell, download the latest 2.x version from https://magento.com/tech-resources/download Then unpack, create a local git repository & commit.


$ mkdir Magento
$ cd Magento
$ tar xjvf ~/Downloads/Magento-CE-2.3.4-2020-01-16-11-26-09.tar.bz2
$ git init
$ git add .
$ git commit -m "Initial commit of Magento"

Normally, you would have to move auth.json.sample to auth.json in the repository to allow Composer to pull from the Magento repository. The PHP buildpack for Heroku will use the value of the COMPOSER_AUTH environment variable instead. It should also be in JSON format, as shown below.


$ heroku create
$ heroku config:set COMPOSER_AUTH='{ "http-basic": { "repo.magento.com": { "username": "<public-key>", "password": "<private-key>" }}}'
$ git push heroku master

Need an authentication key? I relied on the following documentation.

https://devdocs.magento.com/guides/v2.3/install-gde/prereq/connect-auth.html

Are you using WordPress and Magento 2 on Heroku? Tell me about it in the comments!

Categories
devops

NGINX Heroku WordPress

NGINX, Heroku, and WordPress combined. This website is powered by WordPress on Heroku. Details on configuration are here.

My next #DevOps task is to add NGINX in front of the WordPress application. In the future, this could be used as a load balancer. Until then, NGINX will reverse proxy the requests to the Heroku application instance.

To start, I spun up a virtual machine running Ubuntu on Amazon’s EC2. Check out how to install and configure NGINX here. Make sure to open your firewall to HTTP & HTTPS traffic!

I encountered two major issues:

  1. The request passed by NGINX through the reverse proxy was not being understood by Heroku’s application stack.
  2. Once the application stack properly handled the request, WordPress’s response triggered a redirect loop.

Reverse Proxy

Heroku’s stack uses the host of the request to route to the appropriate application instance. The originating Host value is (in my example) ‘wwww.metatooth.com’. Heroku shouldn’t respond to this. Turn off the app’s Custom Domain feature if it does. Update the reverse proxy to set a new Host header that Heroku will respond to.

server {
    server_name www.metatooth.com;

    location / {
        proxy_pass https://calm-waters-18762.herokuapp.com;
        proxy_set_header Host calm-waters-18762.herokuapp.com;
    }

    # configure SSL here
}

Redirect Loop

Setting the Host request header got Heroku’s attention, now WordPress responds to that request with a redirect loop. I encountered this problem while trying to configure an HTTPS-only WordPress installation. The way out of the redirect loop was to update two more request headers and then to use those headers in the WordPress configuration. Here’s the new section of wp-config.php

 
if ( $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https' )
{
        $_SERVER['HTTPS']       = 'on';
        $_SERVER['SERVER_PORT'] = '443';
        define('FORCE_SSL_ADMIN', true);
}

if ( isset($_SERVER['HTTP_X_FORWARDED_HOST']) ) {
        $_SERVER['HTTP_HOST'] = $_SERVER['HTTP_X_FORWARDED_HOST'];
}

That gets WordPress to not redirect to https on these proxied requests, but only if the request headers of X-Forwarded-Proto and X-Forwarded-Host are specified. The NGINX configuration now is:

server {
    server_name www.metatooth.com;

    location / {
        proxy_pass https://calm-waters-18762.herokuapp.com;
        proxy_set_header Host calm-waters-18762.herokuapp.com;
        proxy_set_header X-Forwarded-Host $host;    
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # configure SSL here
}

That’s how I got NGINX, Heroku, and WordPress to play well together. Next task is to use an upstream for the proxy_pass directives. What’s your infrastructure layout and what did you learn along the way? Tell me about it in the comments!