Since I moved this site to Hugo from WordPress last August I’ve been hosting it on a small DigitalOcean Droplet. The other day I decided to try something new and now this site is hosted for free on Netlify and so far I’m extremely impressed.
Why not host it myself?
While the DigitalOcean host was adequate for the job, there were a few issues. First, I was paying ~$8/month to host it (Droplet and backup costs). While that wasn’t a lot it still didn’t perform as well as Netlify and I never had bothered to streamline deployment which had become an extremely manual process. While I enjoy hosting many things myself, and will continue to do so, it just didn’t make sense anymore with services like Netlify available.
Setting it all up
Moving to Netlify was super easy. The hardest part was moving my Git repo back to GitHub from my own Gitea server. For the record, I’ve also shut down the latter as well for now as, while neat, the costs of self-hosting my own Git repos didn’t outweigh the benefits so moving back to GitHub is something I would’ve been doing regardless of where I host the site itself.
Get a Netlify account
This one is easy… Sign up at https://netlify.com and create a new site. Make sure you connect the Netlify site to your site’s GitHub repo. This will allow for automatic deployments when you push to GitHub.
Add the config
You’ll want to add a netlify.toml file to your repo. Here’s mine:
Code language: TOML, also INI (ini)
[build] publish = "public" command = "hugo --gc --minify" [context.production.environment] HUGO_VERSION = "0.62.2" HUGO_ENV = "production" HUGO_ENABLEGITINFO = "true" [[headers]] for = "/css/*" [headers.values] Cache-Control = "public, max-age=360000" [[headers]] for = "/uploads/*" [headers.values] Cache-Control = "public, max-age=360000"
The above configuration has earned me a perfect score on most speed tests with the cache headers being key. Also note I’m specifying the version of Hugo to deploy with. This one is important as you’ll want to match it to what you’re using locally and update accordingly over time. The default version used by Netlify had been failing as some of my templates were just too new.
Push to GitHub
Commit the config file and push your site. If all goes well you should see that it was successfully deployed in Netlify’s control panel.
Point your DNS
Follow the instructions in Netlify’s control panel to point your domain’s DNS to your new site.
That’s it. The whole process took me about 15 minutes and load times of my site went from a fast .75 seconds on average to around .5 seconds. Cutting off a 3rd of the load time is never a bad thing!