Tag Archives: raspberrypi

CI/CD for Amiberry using Github Actions (pt 3)

In the first and second parts of this series, we saw how to set up a CI/CD solution for Amiberry, using self-hosted runners. The workflow will automatically build on every new commit, but also create and publish a new release (including binaries and an auto-generated changelog), based on the git tag. So generally it works… Read More: CI/CD for Amiberry using Github Actions (pt 3) »

CI/CD for Amiberry using Github Actions (pt 1)

The Amiberry emulator supports multiple platforms, so if you want to provide binaries on new releases (like I do), you’ll have a lot of compiling to do. Now, you could just compile a binary manually for each platform you have available, but that would take (very) a long time (especially if you have some slow… Read More: CI/CD for Amiberry using Github Actions (pt 1) »

(Amiberry powered) Lightwave render farm, pt 4

Next we need to install Amiberry itself. If you’re using the recommended Raspberry Pi OS, then you can use the pre-compiled binaries available in the Github Releases page. Otherwise, you’ll need to compile it yourself (check the instructions in the Readme). I recommend you install Amiberry in the same location for each machine, to make… Read More: (Amiberry powered) Lightwave render farm, pt 4 »

(Amiberry powered) Lightwave render farm, pt 3

In the previous article, we talked about the different options regarding the shared content directory that we’ll be using. We will now see some example configurations and how to set them up. Scenario 1: Having the shared content directory on a Linux server This scenario also includes the case where one of the Raspberry Pi… Read More: (Amiberry powered) Lightwave render farm, pt 3 »