Implementing GitHub Actions for Faster Deployments

One of the key challenges I faced during this deployment was the slow file transfer process via Ansible. Previously, I used Ansible to copy all the HTML, CSS, and other assets to the server’s Nginx hosting directory. This method proved to be extremely slow and inefficient.

To address this, I transitioned to using a GitHub self-hosted runner. This approach deploys site updates automatically whenever there is a push to the main branch.

Hosting This Site: Technology Stack and Workflow

This site is hosted using a variety of technologies, each playing a specific role in creating a functional and efficient environment:

• TrueNAS Scale – My primary NAS and hypervisor, utilizing ZFS for redundancy.
• Ansible – Defines the state of the server, providing a pseudo-CI/CD pipeline for this site.
• Hugo – Handles static site generation.
• Docker – Hosts the Nginx and Cloudflare Tunnel containers.
• Cloudflare – Provides DNS and HTTPS tunneling for ease and security.
• GitHub – All configurations are version-controlled in a private repository.

Why Use These Methods

There are easier ways to achieve what I’ve done here, but I intentionally chose a more complex tech stack to learn and practice new technologies. This setup doesn’t necessarily reflect enterprise practices—it’s tailored for personal growth and experimentation.