In this port I'll show you how I write my posts, deploy them to the server, process them with Hugo and host them on my DigitalOcean server.

I wanted this process to be as easy and quick as possible, with as few extra softwares and services as possible. There are a lot of solutions out there like Wercker but I didn't want more things in my way.

# Writing

# Local

I write the posts from IntelliJ IDEA, which is my IDE of choice. Screw Sublime, Atom and all the rest! It's quite heavier but is worth it. You get spell checking, quite good live previews with the Multimarkdown plugin (shame the embedded HTML doesn't render), git integration, and in general a powerful IDE.

Just to be clear I like Sublime and Atom, but every time I use them there is something wrong. Right now the terminal in Atom doesn't work for me. There is an open issue for this but in the meantime you get a blinking unmovable cursor staring at you.

I feel that, since Hugo is quite new, the tools haven't caught up with its popularity yet. Intellij is flexible enough to allow you to have shortcuts live templates for your shortcodes. E.g.:

1  <template name=".shortcode" value="{{&lt; $SHORTCODE$ &gt;}}" description="A Hugo shortcode" toReformat="false" toShortenFQNames="true">
2    <variable name="SHORTCODE" expression="" defaultValue="" alwaysStopAt="true" />
3    <context>
4      <option name="OTHER" value="true" />
5    </context>
6  </template>

This allows me to type .s, press enter (if the live template .shortcode is selected), type the name of the shortcode and its parameters and press enter to keep typing without having to type too many symbols or having to move your cursor.

I keep switching between IntelliJ and the localhost page on my browser, where my hugo server is showing how the end result will be (just launch "hugo server" from the root folder). If you have the page open you don't even need to refresh it thanks to Hugo's live reload feature (and don't even have to save the file since IntelliJ does it when it loses focus). This is very quick to do, which is particularly nice when you want to make final tweaks to make sure your post will display as you want.

# Online

If you are using Github and want to write from your browser, or you are not at home, you can use prose.io. It's a software developed for Jekyll, but works just fine with Hugo. You get some nice shortcuts to format your text with markdown in case you are not too familiar with it. It also allows you to upload images which are committed to your repo immediately. I don't find it quite as powerful as IntelliJ but it's a nice option.

You can have a look at my prose configuration to get you started. It's important to know that prose.io can only generate content with yaml metadata. You will have to configure Hugo to do the same by adding MetaDataFormat: yaml.

I've looked at many more free online content editor:

I found them actually extremely good...just not very compatible with Hugo.

Unfortunately I couldn't find any online resource to write and preview Hugo content, so editing content locally and preview it with Hugo server is still the best option for me. I reckon you could host a test environment to preview your draft, deploying with a different branch, by adding -buildDrafts to your hugo or hugo server commands.

Hopefully some tool that works perfectly with Hugo will come out soon. Spf13, the creator of Hugo, is thinking about creating one.

# Deployment

I can deploy my website in 2 ways:

Push you branch to the repo on the server.
Push the master branch to the main repo. In my case this is on Github but can work with pretty much anything else.

These both trigger a small script which I've adapted from this tutorial on Digitalocean.

 1#!/bin/bash
 2
 3# Better be specific rather than using $HOME because it wouldn't work with all users.
 4GIT_REPO=/home/draga/go-web
 5WORKING_DIRECTORY=$GIT_REPO/public
 6PUBLIC_WWW=/home/draga/public_html
 7BACKUP_WWW=/home/draga/backup_html
 8
 9set -e
10
11# Clean working dir.
12rm -rf $WORKING_DIRECTORY
13# Backup current website. Use -z if moving across network to save bandwidth.
14rsync -aq $PUBLIC_WWW/ $BACKUP_WWW
15# Restore backup if an error occurs from now on.
16trap "echo 'A problem occurred.  Reverting to backup.'; rsync -aq --del $BACKUP_WWW/ $PUBLIC_WWW; rm -rf $WORKING_DIRECTORY" EXIT
17
18# fetch repo to make sure it's up to date if working with remote webhook.
19cd $GIT_REPO
20git fetch
21git checkout origin/master
22# Build the website. GO HUGO!
23/usr/bin/hugo -s $GIT_REPO -d $WORKING_DIRECTORY
24# Mirror the output of Hugo to the directory where the website is hosted.
25# Use -c to copy only files that have changed to avoid messing with webhost caches.
26# Use -z if moving across network to save bandwidth.
27rsync -aqc --delete $WORKING_DIRECTORY/ $PUBLIC_WWW
28# Ask Google webmaster tools to parse your sitemap.
29curl https://google.com/webmasters/sitemaps/ping?sitemap=https://stefano.chiodino.uk/sitemap.xml
30curl https://www.bing.com/ping?sitemap=https%3A%2F%2Fstefano.chiodino.uk/sitemap.xml
31# Disable trap.
32trap - EXIT

I used the method described in the tutorial above for a while, but it bothered me to push twice since I had to type the password for my ssh key (I've disabled the password access to the server and can now only be accessed with the key). Also what if I wasn't home or wanted to use prose.io?

Solution: git(hub) webhooks!

Thanks to github.com/adnanh/webhook, little software written in go, you can have you server listen on a port and execute a script when invoked.

I currently have it connecting in https, with a secret key, and executing the script when the master branch is pushed.

Now I can even use Github itself to edit my posts. Pretty neat!

# Hosting

Now this was the ~~long~~ fun part. I wanted it all so it took a lot of learning, hence the fun.

I heard of nginx a lot and some research showed that it seems to be the go-to solution. Here are some, more performance related, details of how it performs for me: server load test.

I've then enabled the pagespeed module which is very complex and heavy, but definitively worth it! The website now scores 100/100 in Google PageSpeed, both in mobile and desktop!

I score 99/100 in GTmetrix just because there is a bug in the pagespeed module (1064) and the very header is added twice, and for some reason GTmetrix seems to think that is not there...? Or maybe is because pagespeed seems to add it on subsequent reloads. Another small penalty is for the G analytics code being cached for just 2 hours, it's out of my control and don't think is worth self hosting it.

YSlow seems to be mostly concerned of the lack of CDN.

You can find all the scripts that I've used to set up my server on github. They are ordered in the same way they are in the filesystem, so you should get the idea. There is a script to install nginx with the brotli and pagespeed module, directives to use webhook as a service, the entire nginx configuration, etc.