Ansible

Establishing PHP dev and pod environments Still continuing my 2024-jul-13 journey. Because there are no any Dev/Prod enviroment whatsoever… I need to create one. At the same time I have no experience with PHP runtimes and need to learn a bit about it. At this day, I managed to create working containerized Nginx, PHP-FPM and MariaDB workload to run PHP applications. I used Ansible roles/playbooks and Podman Quadlets (Systemd units) for the container management as they don’t need Kubernetes for sure....

There are several ways to pass the Ansible Vault password. classic CLI prompt which requires manual intervention password file which should be stored somewhere accessible to the Ansible environment variable Today I will tell about my latest approach. I am using tool called Direnv which loads and unloads different environment variables when you enter the directory. Direnv uses .envrc files to read the variables from. Typically, this file should be in your ....

My opinion on this is still not stable or true and I might change my mind later when I will really try NixOS. I see the constant hype around the NixOS and one of the main selling points is its reproducibility. Under the Ansible, you configure only whats in your playbooks. And it’s easy to mess around the system bypassing the Ansible. In NixOS that’s not the case. If you make any add-hock changes on NixOS and then run nixos-rebuild all your crafted changes will be gone because they are not in your NixOS config....