Continuous Integration and Continuous Delivery are very trendy topics in the DevOps world right now. There are quite a lot of services and software to build, test and deploy your code, but actually, a few are free and open-source and self-hostable. The most well-know softwares corresponding to these characteristics are Jenkins and GitLab CI. However, Jenkins has a huge memory footprint since it runs on Tomcat (Java). As for GitLab CI, it’s very good but requires you to run your own GitLab (which is huge) or to be on gitlab.
Posts with the tag linux:
Warning Edit (2020): I highly discourage using Wasabi. They have a very misleading pricing policy and you will end up with bad surprises on your invoices at the end of the month. For the past few months, I have been using Borg to backup my servers. It was working great and was pretty reliable, but a bit complicated. My previous setup: SSH + Rsync + Borg Here’s the setup:
I’m currently running Ubuntu 18.04 and I noticed that by default I was using systemd-resolved for DNS: [email protected] ~> cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use.
Warning Edit (2020): I highly discourage using Wasabi. They have a very misleading pricing policy and you will end up with bad surprises on your invoices at the end of the month. As you may know I have been running a Mastodon instance for over a year now and in such a long period of time the instance accumulated a lot of data. The context The DB contains about 20 million toots for about 20 GB.
Why? Why would you run Docker on ZFS? I discovered ZFS when I was playing with LXD, because it’s the recommended storage driver for it. While ZFS has a lot of great features, the ones I like the most are the RAM cache, compression, and snapshots. After moving from LXD to Docker (so leaving ZFS), I felt the difference in speed the cache gave me, and I saw some files like databases being 3 times bigger.
ZFS is great file system that comes with a lot of benefits, and I’ve come to use on my servers with LXC or Docker. Even if RAIDZ or self-healing are useless on a VM, we can still benefit from compression, snapshots, cache, etc. The proper way to create a ZFS pool is to dedicate a device or partition to the zpool. I’m using the new Hetzner cloud offer a lot recently and that’s also where I use ZFS.
I’ve been using Munin for the past years as my monitoring tool. It works well, it’s light, and super easy to set up. It’s a bit old and limited though, so it’s time to look at what kind of monitoring software we have in 2018. Instead of having one software that does everything nowadays we like to separate the roles this way: The collector, which you will install on the machines you want to monitor The database that will store all the measurements The visualization system, e.
I’ve been moving my services to Docker lately because it suits my needs an ease my life a lot, but I was kind of stuck when wanting to move my Diaspora pod into containers. Indeed, the Diaspora project doesn’t have any official Docker image, including a Dockerfile, docker-compose.yml or any kind of instructions or guide, because none of the core developers actually use Docker so they’re still searching for someone to maintain one.
If you’re not using a CMS like WordPress, chances are your CMS or blog engine doesn’t support comments. That makes sense if it’s a static blog built with a tool like Hugo, Jekyll or Zola, but does less when your blog is powered by a database, like Ghost is. I think comments are part of a blog and it’s important to enable them. Readers can thank you for your work, report a mistake, discuss the article, etc.
There are different storage types for LXC containers, from a basic storage directory to LVM volumes and more complex file systems like Ceph, Btrfs, or ZFS. In this post, we’re gonna setup a ZFS pool for our LXC containers, via LXD. Why ZFS? ZFS is an awesome file system. It’s a 128 bits file system meaning that we can store a nearly unlimited amount of data (no one will never attain its limit).