Setting up a hugo based website on ubuntu then auto deploy using gogs' webhooks

Posted by Daniel T. Morgan on Thursday Feb 18 2016
In
Tags go, golang, hugo, digital ocean, ubuntu, git

What is Hugo?

Hugo is a static HTML and CSS website generator written in Go. It is optimized for speed, easy use and configurability. Hugo takes a directory with content and templates and renders them into a full HTML website.

Hugo relies on Markdown files with front matter for meta data. And you can run Hugo from any directory. This works well for shared hosts and other systems where you don’t have a privileged account.

Hugo renders a typical website of moderate size in a fraction of a second. A good rule of thumb is that each piece of content renders in around 1 millisecond.

Hugo is designed to work well for any kind of website including blogs, tumbles and docs.

https://gohugo.io/

What is Gogs?

The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service. With Go, this can be done with an independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, Windows and ARM.

https://gogs.io/

It is a great self hosting github/gitlabs sort of project but coded in go.


I started by following this digital ocean tutorial

I didn’t want to use a package, my preference was to compile from source. However I got the following error while trying that: go: missing Mercurial command. See https://golang.org/s/gogetcmd package bitbucket.org/pkg/inflect: exec: "hg": executable file not found in $PATH Thanks to this and google translate I realised Mercurial was a dependancy.

so sudo apt-get install mercurial and then

go get -u -v github.com/spf13/hugo

got me cooking!

In the DO tutorial it says to run

sudo hugo genautocomplete

this seems to be factored out to

sudo hugo gen autocomplete

but because I compiled from source hugo isn’t in sudo environment path so

sudo ~/go-workspace/bin/hugo gen autocomplete

[~/go-workspace is my $GOPATH so change to yours]

While cloning the themes I decided hugo-themes was a better name for the directory in my home dir (themes could be anything while browsing later), of course this meant later, my symlink would need to look like:

ln -s ../hugo-themes/ themes

It seems that some other switches are different from the DO tutorial (-themes= in git cloned version is -t )

Auto deploy

This is based on the digital ocean tutorial here the difference however was, is I use gogs, the server itself has no firewall access to my gogs server. I decided to solve this problem using the tutorial/gogs’ web hooks/and a little php (that I’m sure I’ll refactor as go at some stage)

First of all lets set up the gogs web hook:

Inside the repository in question click on the settings link on the right hand side

Gogs Settings

Then click on the Webhooks link on the left hand side

Gogs Webhooks

Finally enter a url the gogs server can connect to and that you can write php on (make a note of the Secret that you use)

Gogs Webhook

Now the php that runs at the URL you entered above should look a little something like this.

*update I noticed that syntax hilighting was going missing on this post (turned out that pygmatize was not in path of the php process) (php runs as my user account) so I fixed this by changing

$command = "cd $WORKING_DIRECTORY; /path/to/hugo"; echo `$command`;

to

$command = "cd $WORKING_DIRECTORY; export PATH=\"What my $PATH is at tty\" hugo"; echo `$command`;

This felt a little dirty but after many attempts at a more elegent solution, I have stayed with this for the time being.