pim/blog
2
0
Fork 1
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Update pages of AboutIdeasNow
All checks were successful
/ blog-pim (push) Successful in 10m51s
Details

Browse source
This commit is contained in:
Pim Kunis 2024-05-11 22:39:41 +02:00
parent 5814047d07
commit 47bbe26567
4 changed files with 47 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

16
src/ideas.md
View file

@ -6,4 +6,18 @@ excerpt: Plans for the future
comments: false
---
🏗 Under construction 🏗
**Infrastructure as Code (IaC)** is the most important principle I adhere to when building my home lab.
With IaC, all (digital) infrastructure and systems are defined in code that can be automatically rolled out.
Ansible is probably the most used IaC tool out there, but it has a huge problem: it suffers from configuration drift.
You can create a task in Ansible to install a package, but if you remove this task, the package remains.
At this point, your configuration does not reflect reality anymore.
What is the solution to this configuration drift? Nix and NixOS!
NixOS will always make sure you machine is in the exact state you define in your configuration.
My current Linux systems now all run NixOS and I have no intention of ever going back!
And obviously, I won't be able to make a home lab without **open source software**.
While I'm very appreciative of the goals of Free and Open Source Software (FOSS), it's unfortunately not realistic to make a home lab solely with FOSS.
I do try to draw a line at "corporate" open source software.
This is a very blurry line, but I feel Jeff Geerling explains this well in [this video](https://www.youtube.com/watch?v=hNcBk6cwim8).
I was betrayed by Hashicorp's open source offering, and I'm very hesitant in adopting for example Tailscale as a result.