I’m hosting this blog on AWS S3 and Cloudfront. One disadvantage with S3 is that it doesn’t have a simple way of creating redirects — like Netlify, Firebase, or even Nginx.

But there is way; using the AWS CLI, put-object, and the x-amz-website-redirect-location metadata.

Here’s how 👇

This blog is built with Hugo — an open-source static site generator. Static websites require no server side processing, which makes them easier to host and opens up new hosting possibilities.

There are many options out there, but I deploy my website to AWS S3, using CloudFront to distribute it globally (aka. make it fast).

Here is the why and the how.

In my previous post I wrote about turning Hugo aliases into Firebase redirects. Now — let’s convert them into a Nginx map file, and have Nginx redirect based on that file.

Using Firebase and Hugo? Use front matter aliases to automatically add redirects to your firebase.json configuration. Turning your aliases into proper 301 or 302 redirects.

I’ve been hosting repository mirrors from my homelab rack for a while. I first set up Archlinux in May 2018, then followed OPNsense, Cygwin, MariaDB, Raspbian and lastly Manjaro — now they are in a Terrahost datacenter instead.