Posts

ssh’ing into my Digital Ocean droplet has become rather annoying for maintaining this website. Particularly annoying is dealing with images on two different filesystems. In the README (commit 1a0ee5a), I describe the steps I have been doing to publish an article to https://brege.org. I tried implementing this method, but it is very long and requires many modifications to the post-receive hook to get it working on a per-user basis. Here I outline a way to do this in a more conservative manner. ...

Firefox Developer Edition has newer features than what was available from my distribution’s package manager (Fedora). Whereas I’ve been using it as my daily driver, I’ve had to do so through a terminal to launch it. With an alias in my ~/.bashrc such as dfox="~/Preview/firefox-developer/firefox --profile ~/.mozilla/firefox/7ahl24yk.default/' I was able to launch Firefox Developer quickly enough. Unfortunately, I found it annoying that I couldn’t just type [Super Key] + “Fire” in GNOME and be on my way to browsing the web. ...

Earlier I added the hugo source files for this website on GitHub. Take a look! https://github.com/brege/brege.org

Add the following to the main server block in your nginx config: location ~ ^/(?:feed|feeds|rss) { return 301 /post/index.xml; } Now people can go to https://brege.org/rss to find the RSS feed. This rewrite rule could be expanded to match other common feed URI guesses.

Let’s Encrypt certificates need to be renewed every three months. The Arch Wiki has good documentation on automating the renewal process with systemd. ...

Overview brege.org is deployed with the following services: Namecheap - DNS Registrar Let’s Encrypt - Free SSL certificates Digital Ocean - Droplets for $5 a month brege.org makes use of the following tools: Nginx - Fast reverse proxy Debian Jessie - Operating system running on our DO droplet Hugo - Static site generator ...