Wow! It’s been over a year without an update. Time flies. Sorry ‘bout that. Trying to keep myself busy with Armbian-related stuff.
Save the date! At 2027-06-26 the Zuckerbude website will be 20 years old :-)
Armbian - using kernel-config
About a year ago the Armbian build framework made its transition to the next generation. Tons of code have been rewritten, new features added, existing one were rewritten in Python from scratch. The main driving force behind it was Ricardo Pardini.
With this transition some build options regular users were quite familiar, KERNEL_CONFIGURE or CREATE_PATCHES for example, were deprecated and this lead to confusion and incomprehension, last but not least due to the more or less constant lack of detailed framework documentation. So users had to conjecture how things work from reading the code, forums and answers to issue reports.
This situation even forced the Armbian developers to bring back the old switches to some extend.
In today’s topic I want to break down kernel-config as the now modern way to configure your Linux kernel configuration before building.
Just got rid of my Reddit account including all my content.
Neither do I see any advantage in using it anyways nor do I support their upcoming changes in API pricing.
Screw Reddit!
Just a short follow-up to the Hetzner - Jitsi - story below.
Started exploring the usage of hcloud to compress the full setup down to a single command (presupposed that IPv4/IPv6 already exist and have proper A/AAAA-records attached).
Well, it works flawless :-)
Create a local cloud-init.yaml file and fill it with the #cloud-config stuff down below in the article.
Get yourself the hcloud tool and run:
hcloud server create --datacenter 4 --image jitsi --name jitsi \
--type cax11 --user-data-from-file cloud-init.yaml \
--primary-ipv4 121345678 --primary-ipv6 12345679
Replace the server type and datacenter with something appropriate for the intended size and location of your meeting.
Use hcloud primary-ip list to get the IDs.
Once your meeting is done you can get rid of the server with hcloud as well:
hcloud server delete 12345678
You can grab the ID of the server via hcloud server list or you are smarter than me and remembered the ID from the output of the create command.
Next setup would be the automated setup of an RTMP server to allow recording…
Deploy Jitsi on demand in Hetzner Cloud
Recently the so called BigBrotherAwards have been awarded. In the pool of winners this year were also the well known Zoom video conference tool. This made me thinking, because the Armbian project uses Zoom for their weekly developer meetups.
So I decided to invest a bit of time to explore if it would be possible to deploy a self-hosted Jitsi video-conference server on a Hetzner cloud server on demand, without much configuration needed. And this is what I came up with.
Continue readingWelp, in theory at least I planned to make a review about the Orange Pi 5 but still could not find proper mood to do so…