==========================
== Timoteo Ponce's blog ==
==========================

Deploy site using Github Actions

guide

A while ago I had a personal site in some obscure Russian hosting site, I don’t even remember if I have paid for that hosting or if it was something with ads. Nevertheless, since then the idea of having a public and personal website has always attracted me.

So, once the motivation is set, a new site is gonna be created, this is how we can proceed to create a personal website:

Domain

The first step in all web-related ideas is to buy a domain, nothing is really done unless it’s public. In the past it was really complex to get a domain, but nowadays it’s quite simple, while there are many choices to buy and manage domains, Namecheap it’s one of the cheapest ones. Our domain at https://timoteoponce.com costed around 12 USD a year, so we bought it.

Server host

Now, on the hosting part we have many options as well, some of my favourites ones these days are:

Why these providers? Because they provide you empty servers, we must handle everything from scratch. We went with Digital Ocean with the cheapest server as well and proceeded to configure a simple Ubuntu Server instance.

Web server

Once that is done, we need to install a web server, while Apache is still the great player, (Nginx)[https://nginx.com] is a superb tool for the matter, following the following tutorial was just enough:

This was a piece of cake (this used to be a bit hard back in the day) by following the official guide:

HTTPS

Another thing that is quite simple and mandatory for any site now, HTTPS, and it’s so simple. Proceeded to perform this task with the amazing Let’s Encrypt:

Dynamic or static content?

Finally, we have the whole infrastructure is ready, we can finally start adding some content to our site!

What to do then? In the past, to install a CMS would have been the first choice, but not all sites require the overhead and complexity of a full CMS, our intent is mainly to publish content that’s mostly static, and being ourselves in the development environment, something like a static site generator is a great approach.

Once our content is set (I’m using Jekyll) we push it to Github and then create an action to deploy it to our shiny server, yet again, here’s the guide to do it: