Projects & Stories

Gitlab runner clean-up caches

photo_small If you are using the gitlab runner on your system you probably already saw the pile of cache containers he leaves after running pipelines. Thats nessecary cause .. well its a cache and could be reused. But I think after a certain amount of time its ok to clean-up the mess. If you search for it you probably end up with the gitlab-runner-docker-cleanup repository. It will clean-up cache containers after a certain threshold is reached. Since the git []

Receive Email via AWS and import it into your Mailserver

photo_small This time my goal was to receive and send email via AWS. Sending mail is qickly done with your MTA but receiving mail is a bit more tricky. First of all I configured two MX records one for AWS and one for my own server which should act as backup server: lukas ~ > dig MX [...] 10800 IN MX 50 10800 IN MX 10 []

ODB2, DealerTool and Linux

photo_small Sometimes I am wondering myself why people pay a lot of money for closed-source software when they can use open-source for free. This time I simply wanted to read my ECU for errors and some sensor information. If you quickly search for "Triumph" and "ECU" you will end up with expensive Window Programms. But if you dig a little bit deeper. You will know that reading your ECU is pretty much standardized, whether it is a car or y []

Flash your recovery image via adb shell on android

photo_small //edit: You need a rooted device for this kind of flashing Hi, ever wondered about how you can flash a recovery.img via adb shell? A lot of posts suggest flashing it via fastboot. Well my shitty Samsung phone is not detected by fastboot. Then there is the option to install a dubious binary file which is called flash_image.. thank u internet! Well damn I have the recover.img whats so hard to use dd and flash it with a single shell command? For tho []

Sidekiq 3 Memory Killer

photo_small My Sidekiq 3 installation seams to be very hungry in respect of memory. If you dig through the Net you'll find a lot of similar reports. For e.g. the unicorn web worker a memory-killer script exists which should prevent running into Madland. So I thought I take an example and do a similar thing for the sidekiq workers. If you give them time and send a graceful kill signal there shouldn't be any data-loss either. #!/bin/bash # check if script is []