Şahin Akkaya’s Personal Page

Automatically Build and Deploy Your Site using GitHub Actions and Webhooks

2022-01-04T17:40:00+00:00

In this post I will explain how you can use GitHub to automate the build and deployment processes that you have. I am going to automate the deployment of this site but you can do whatever you want. Just understanding the basics will be enough.

Introduction to GitHub Actions and Webhooks

Let me start by explaining what are GitHub Actions and GitHub Webhooks.

Github Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.

Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization. … For example, you can configure a webhook to execute whenever:

A repository is pushed to

A pull request is opened

A GitHub Pages site is built

A new member is added to a team

Defining the problem and solution

As I said, my example will be automating the deployment of this site. Here is the normal workflow of me doing it manually:

As you can see, the only place where my work is really required is writing the post. Other two steps can be automated. We will use GitHub Actions to generate the site content and Webhooks to let our server know about the new content so it can pull the changes. Let’s get started.

Setting up GitHub Actions

Setting up a GitHub Action is as easy as creating a .yml file in .github/workflows/ directory in your repository. Let us create a new action to build our site. Fortunately, there is already a GitHub action to do it for us. Create a file called .github/workflows/jekyll.yml in your root directory of your repository and put the following contents:

name: Jekyll site CI

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Jekyll Actions
      uses: helaili/jekyll-action@2.2.0
      with:
        token: ${{ secrets.GITHUB_TOKEN }} 
        keep_history: true
        target_branch: 'gh-pages'

That’s it! We have created our first Action. When we push this change, GitHub will start building our site and push the result to gh-pages branch. Currently, it will take a while to build because we don’t use caching. So let’s include it to build faster. Add the following piece as a second step:

# Use GitHub Actions' cache to shorten build times and decrease load on servers
- uses: actions/cache@v2
  with:
    path: vendor/bundle
    key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile') }}
    restore-keys: |
      ${{ runner.os }}-gems-

We are done with the Actions part. You can see the final code here. When you are also done with the code, just push it to trigger the action.

Now that we set up our Action to build the site, we need to let our server know about the changes so that it can pull the changes.

Creating a Webhook from GitHub

To add a Webhook, open your repository in browser and navigate to ‘Settings > Webhooks’ and click ‘Add Webhook’. Fill in the form with appropriate values. Here is an example:

This is all you have to do from GitHub. Now, whenever there is a push event to your repository, GitHub will send a POST request to your payload url with the details.

Note: Our Action is configured to push to a branch in our repository, so it will also trigger this hook and we will catch it.

Creating an endpoint to handle the requests

I will use Flask framework to handle the post requests coming to our endpoint. You can use whatever programming language or framework you want. It will be very simple code with just one job: Validate the secret keys and run a specific code.

Let’s start by creating a new project and a virtual environment:

mdkir post_receiver
cd post_receiver
python3 -m venv venv
source venv/bin/activate

Install the required packages:

pip install Flask gunicorn

Create a new file for storing our environment variables:

# config.py

APP_KEY = "your-secret-key" # same key that is used in github while creating the webhook
PROJECT_PATH = "/path/to/your/project/" # you will want to cd into this path and perform commands such as git pull etc.

And create the Flask application:

# post_receiver.py

import hashlib
import hmac
import subprocess

from flask import Flask, request

import config

application = Flask(__name__)

@application.route('/', methods=['GET', 'POST'])
def index():
    if request.method == 'GET':
        return 'OK'
    elif request.method == 'POST':
        content = request.data
        secret = bytes(config.APP_KEY, 'utf-8')
        digester = hmac.new(secret, content, hashlib.sha256)
        calculated_signature = 'sha256=' + digester.hexdigest()
        signature = request.headers.get('X-Hub-Signature-256')
        if calculated_signature == signature:
            subprocess.Popen(
            ['./perform-git-pull.sh', config.PROJECT_PATH])
            return 'OK'
        else:
            return 'Error'

if __name__ == "__main__":
    application.run(host='0.0.0.0')

I will not go into details explaining what each line does. Basically, we are checking if the request is a POST request and if so we are comparing the secret keys to make sure that the request is coming from GitHub. In our case, this is not too important because when the keys match we are running simple git commands in our repository but you might need it if you are doing something more complicated. And here is the contents of perform-git-pull.sh file:

#!/bin/bash

cd $1
git checkout gh-pages
git pull

We are almost done! All we need to do is create a service to automatically run our code and let nginx handle our endpoint correctly.

Create a new file post_receiver.service in /etc/systemd/system/:

#/etc/systemd/system/post_receiver.service

# change <user> to your actual username
[Unit]
Description=post_receiver
After=network.target multi-user.target

[Service]
User=<user>
Environment="PYTHONPATH=/home/<user>/post_receiver/venv/bin/python"
WorkingDirectory=/home/<user>/post_receiver
ExecStart=/home/<user>/post_receiver/venv/bin/gunicorn -b 127.0.0.1:5000 -w 2 --log-file /home/<user>/post_receiver/post_receiver.log post_receiver

[Install]
WantedBy=multi-user.target

Make sure port 5000 is reachable from outside.

sudo ufw allow 5000
sudo ufw enable

Finally, edit your nginx configuration, /etc/nginx/sites-available/yoursite

location =  /postreceive/ {
    proxy_pass          http://localhost:5000/;
}

Start, restart the services

sudo systemctl daemon-reload
sudo systemctl start post_receiver
sudo systemctl enable post_receiver
sudo systemctl restart nginx

That’s it! curl https://yourdomain.com/postreceive/ should return "OK" and we are ready to accept POST requests from GitHub.

Notes for debugging

In case anything goes wrong, here are a few tips to debug:

Every GitHub Action produces a log that you can examine. Check them to see if anything is odd.
In the Webhooks tab, there is a sub-tab called Recent Deliveries. You can take a look at there to see the results of the requests from your hooks.

You can always test your code locally with curl:

❯ curl -i -X POST -H 'Content-Type: application/json' -d '{"foo": "bar", "bar": "baz"}' https://yourdomain.com/postreceive/

Happy hacking!

Stop cat-pipe’ing, You Are Doing It Wrong!

2022-01-01T15:00:00+00:00

cat some_file | grep some_pattern

I’m sure that you run a command something like above at least once if you are using terminal. You know how cat and grep works and you also know what pipe (|) does. So you naturally combine all of these to make the job done. I was also doing it this way. What I didn’t know is that grep already accepts file as an argument. So the above command could be rewritten as:

grep some_pattern some_file

… which can make you save a few keystrokes and a few nanoseconds of CPU cycles. Phew! Not a big deal if you are not working files that contains GBs of data, right? I agree but you should still use the latter command because it will help you solve some other problems better. Here is a real life scenario: You want to search for some specific pattern in all the files in a directory.

If you use the first approach, you may end up running commands like this:

❯ ls
 config.lua   Git.lua          init.lua   markdown.lua   palette.lua      util.lua
 diff.lua     highlights.lua   LSP.lua    Notify.lua     Treesitter.lua   Whichkey.lua

❯ cat config.lua | grep light
❯ cat diff.lua | grep light
❯ cat Git.lua | grep light
❯ cat highlights.lua | grep light
  Pmenu = { fg = C.light_gray, bg = C.popup_back },
  CursorLineNr = { fg = C.light_gray, style = "bold" },
  Search = { fg = C.light_gray, bg = C.search_blue },
  IncSearch = { fg = C.light_gray, bg = C.search_blue },

❯ cat init.lua | grep light
local highlights = require "onedarker.highlights"
  highlights,
❯ # You still have a lot to do :/

If you use the second approach, you will immediately realize that you can send all the files with * operator and you will finish the job with just one command (2 if you include mandatory ls :D):

❯ ls
 config.lua   Git.lua          init.lua   markdown.lua   palette.lua      util.lua
 diff.lua     highlights.lua   LSP.lua    Notify.lua     Treesitter.lua   Whichkey.lua

❯ grep light *
highlights.lua:  Pmenu = { fg = C.light_gray, bg = C.popup_back },
highlights.lua:  CursorLineNr = { fg = C.light_gray, style = "bold" },
highlights.lua:  Search = { fg = C.light_gray, bg = C.search_blue },
highlights.lua:  IncSearch = { fg = C.light_gray, bg = C.search_blue },
init.lua:local highlights = require "onedarker.highlights"
init.lua:  highlights,
LSP.lua:  NvimTreeNormal = { fg = C.light_gray, bg = C.alt_bg },
LSP.lua:  LirFloatNormal = { fg = C.light_gray, bg = C.alt_bg },
markdown.lua:  markdownIdDelimiter = { fg = C.light_gray },
markdown.lua:  markdownLinkDelimiter = { fg = C.light_gray },
palette.lua:  light_gray = "#abb2bf",
palette.lua:  light_red = "#be5046",
util.lua:local function highlight(group, properties)
util.lua:    "highlight",
util.lua:    highlight(group, properties)

Isn’t this neat? You might say that “This is cheating! You are using a wild card, of course it will be easier.” Well, yes. Technically I could use the same wild card in the first command like cat * | grep light but:

I figured that out only after using wild card in the second command. So I think it is does not feel natural.
It is still not giving the same output. Try and see the difference! *

First blog post

2021-12-24T23:54:08+00:00

Hello, World!^* So here I am and welcome to my first blog. Having a personal space on the Internet has been a dream for me for years and I am happy that it finally have come true. You might think that I could sign-up for a social media platform and my profile would be a personal space for me but no. I just don’t feel comfortable with that way. This has been the case since my childhood and also the reason why I don’t use Facebook, Instagram or any other social media. If you think you found me on these platforms, I would say it is not me. I might write another post about why I don’t like social media but I will cut this one here.

Why I wanted to start blogging?

There are several reasons for starting my own site and blogging, but I can list the most important ones as follows:

Giving back to community

I use the software developed and brought by the community every day. The moment I power on my computer I start using Free Software. It really amazes me to see the work produced by people who do not know each other at all. For example, I did not even write a single line of code for this site. If Free Software didn’t exist, I’d either have to spend money and use a platform that I have limited control over, or waste my time and build a site with a possibly worse design than this one^*. In return for this, I want to give back to the community. For me, the way to give back to the community so far has been to share the projects I’ve done and archive the things I learn every day in a repository called TIL ^*. But some of the til’s I’ve written recently are getting lengthy and I think they deserve their own posts. So instead of writing long til’s, I will blog what I learned here.

Archiving the memories

I like to go over what I have done in the past once in a while. Blogging is perfect way to do this. I still read my diaries that I wrote in the past and they are fun. But I promise I will keep these posts more formal than my diaries^*.

Pushing myself to do something useful

At the end of every year, I sit on my desk and think about what I did in that year. I generally don’t like the result because I fail to keep some of my resolutions for that year. Setting up a personal website was one of my resolutions for 2021 and it looks like I manage to keep it^*^*. Unfortunately, I can’t always keep my spirits up. Sometimes I just do nothing and all the time passes. Hopefully, the feeling that I have to write something will help me get out of bad mood at such times.

Improving my writing skills

Last but not least, I want to improve my writing. Even though I don’t use a formal language while writing here, I think it will help me improve my writing skills.

Final words

While writing this post I already come up with some new topics to write but I think they need their own posts.

Subscribe to my RSS Feed to not miss them. You know RSS, right? I recently started using it and it is the best way to consume content. Do yourself a favor and search it if you don’t know. I will probably write something about it in the following blog posts. That’s all from me and thank you for reading. See you next time!