For a number of services, I need a system/service which can receive web hooks, and act when such a trigger is received.
For a number of services, I need a system/service which can receive web hooks, and act when such a trigger is received.
GNU parallel allows you to multiplex tasks, and possibly use more CPU resources to speed up the task at hand. This works if your task can be split down into multiple independent tasks which otherwise will be executed serially.
In one of my Ansible Playbooks I’m updating Let’s Encrypt certificates. Because the Playbook is rather long, I want to make sure that Ansible is not spending cycles on a certificate which is not about to expire. Hence I wrote a small filter plugin, which receives the certificate path and the number of days the certificate must be still valid.
This plugin is used to filter out any “good” certificate which does not need to be updated.
At FOSDEM someone asked how long 64 bit Transaction-IDs will last.
To refresh: PostgreSQL is currently using 32 bits for the TXID, and is good for around 4 billion transactions:
Update: Blog post using the acme_certificate module can be found here.
Ansible comes with a plugin which allows to create and renew Let’s Encrypt certificates. Documentation is sparse, so I decided to post about my own Playbook.
Vacation time ahead, and the iPad in the house (who ever had the idea of buying one?) needs a proper VPN connection, in order to be able to access Netflix in Germany.
On Android it’s fairly easy: install the app, drop CA cert, private cert, and key on the device, add everything - done. Three devices ready in less than 10 minutes.
And then I tried the iPad …
Concourse by default hides newly created pipelines from the public. That’s not in the interest of Open Source projects, which want to show the entire build process.
Up until recently I was using an App to clean the the Android cache once in a while. If you don’t, the device over time get’s sluggish, because too many apps store too much data in the cache. Over time this cache can grow to GBs in size.
On the other hand, every single “clean cache App”, over time, started showing more and more aggresive advertising. I get that the developer wants to make some money, that’s fine. But maybe the money is not enough, so more advertising it is.
Recently it was time to refurbish our email infrastructure. For a very long time I was hosting everything for myself, but things don’t get easier and over time even the spam filters couldn’t catch up. Therefore I looked into a number of hosted services, and in the end settled with Google Gmail.
End of last year I ran a test, migrated one of my domains over to Gmail and tried out if Gmail offers all the required functionality. As with every change, not everything works flawlessy, but mostly I found ways to get things working. As example we have different domains, several users, multiple identities (one per domain), other servers (like a webserver) can create emails as well (needs to play well with SPF and DKIM), a number of different email programs, mobile support and more.