I had to wait a little while for the ARMv7 version for my EfikaMX devices, but they finally had time to compile it. Yay!
- Better key management
- No more separate dump1090 launch
- newest fr24 version
However, it’s now time for something new.
As always, as minimalistic as possible.
On a side note, this blog has been moved from vm1 (and one before that) a virtual machine running on a dual Xeon 3070 (2.66Ghz) at Databarn to Akama, a VM on an 8 core Xeon E3-1230 (3.2Ghz) at Leaseweb.
I’ve also correctly repaired IPv6 on this blog. Apparently nginx never and/or stopped correctly listening to IPv6 (suddenly my Android devices displayed errors on this page, Chrome & Firefox on OS X seemed to fall back to IPv4 instantly… Not sure how long it was broken, but it’s back).
Note to self:
listen yeri.be:443; server_name yeri.be;
Does not work with IPv6, it has to be
listen [::]:443; server_name yeri.be;
This Ansible playbook is untested on its own. It comes out of a way bigger (private) Ansible playbook, and I kind of just copy pasted this part, as others might benefit from it.
After running Ansible, you should reboot for driver blacklisting to work in cases it’s needed on your device (it is on RPis). And be sure to edit
/root/flightradar24.sh with your key.
Note to self: <1Gb of RAM on a Dom0 Wheezy server causes kernel panics.
Using 2Gb of RAM seems to do the trick.
If you have a rc.local looking like this:
and files in /etc/rc.local.d looking like this
hostname.sh sshkeys.sh firstboot.sh
it’s not going to work.
Why, you ask, after cursing and shouting for the past hour?
because run-parts ignores files with dots (“.”) and/or .sh files.
Yes. True story.
rename all the files to:
hostname sshkeys firstboot
and your problem will be solved (and of course chmod +x them).