In my spare time I develop applications on Android. I also “maintain” F-Droid repository for some of my public projects. I wanted to automatically publish each build after:
- Compilation passed
- Test on a connected device passed
- Signed build completed
So I made a simple setup with help of GitLabCI and own F-Droid repository. This post does not describe how to configure F-Droid repository or configuration of GItLabCI-runner, because official documentation is much better than I could write it. This post just describes how I use both services to automate boring deployment.
GtiLabCI is run on your own hardware, so it can have access to your files, configuration etc. It’s an advantage over Travis, as you can run any custom command, like testing on connected device or on pre-configured emulator, connected to remote hosts where CI slave is on a trusted machine.
I like to automate some boring and easy tasks we all have to do often, so I would like to share with you an easy but not too widely known trick in Debian/Ubuntu for automated upgrades, that can be performed without any manual actions.
This post describes the following configurations for a server:
- Installation and configuration of unattended upgrades on Debian
- Setup of Tor service that will be used for Debian upgrades
- Removal of unused dependencies
Unattended upgrades are well described on Debian wiki, but to keep those steps in one place, I’ll copy some parts of it here.
First, you have to install the following packages:
apt-get install unattended-upgrades apt-listchanges
Installation process should create new file /etc/apt/apt.conf.d/50unattended-upgrades where we configure how automated upgrades work and what can be upgraded.
I made a timelapse video using Raspberry Pi from my sea-front flat in Aberystwyth where I studied for 4 years.
Bash script was called every 30 seconds to take a picture for 4 days. To prevent running out of space on a SD card there was another cron job setup to move all existing images to my laptop using scp. After some selection (removed some first and some last images) I got 17.4GB of pictures which were composed into this timelapse without any scaling.
…that’s why we published our product on OSI-compatible license! We <3 open-source!
Well, does Microsoft/Google/Apple/Netflix/XXX really love open-source?
No, they don’t. In fact they do more to extinguish open source by fighting them with patent wars, you don’t hear about, developing DRM, you hear about when it’s too late and dropping support for some key-products on open source platforms. Skype on Linux, anyone? Google Drive client on Linux? DRM enabled by default in browsers, anyone?