Using My New Raspberry Pi To Run an Existing GitHub Action

This post was originally published on DZone (IoT)

Recently, I mentioned how I refactored the script that kept my GitHub profile up-to-date. Since Geecon Prague, I’m also a happy owner of a Raspberry Pi:

Though the current setup works flawlessly — and is free, I wanted to experiment with self-hosted runners. Here are my findings.

Context

GitHub offers a large free usage of GitHub Actions:

GitHub Actions usage is free for standard GitHub-hosted runners in public repositories, and for self-hosted runners. For private repositories, each GitHub account receives a certain amount of free minutes and storage for use with GitHub-hosted runners, depending on the account’s plan. Any usage beyond the included amounts is controlled by spending limits.

About billing for GitHub Actions

Yet, the policy can easily change tomorrow. Free tier policies show a regular trend of shrinking down when:

A large enough share of users use the product, lock-in Shareholders want more revenue A new finance manager decides to cut costs The global economy shrinks down A combination of the above

Forewarned is forearmed. I like to try options before I need to choose one. Case in point: what if I need to migrate?

The Theory

GitHub Actions comprise two components:

Read the rest of this post, which was originally published on DZone (IoT).

Previous Post

Power BI: Transforming Banking Data

Next Post

Breaking Down Data Silos With a Unified Data Warehouse: An Apache Doris-Based CDP