rcm VS Ansible

Are your per-machine branches mostly distinct, or do they share a lot?

I use https://github.com/thoughtbot/rcm and I find my dotfiles share _quite a bit_ in some respects (e.g. neovim config) but are drastically different in others (SSH config as one example) -- keeping things synced _across_ branches sounds very difficult. rcm handles this well, without branches, IMO.

I use https://github.com/thoughtbot/rcm, which works smoothly and includes support for host-specific files

I use thoughtbot/rcm to handle my github dotfiles. Super short version after installing, mkdir ~/.dotfiles Then go through your home directory (ie. ~/ ) and mkrc .bashrc and then do the same for any other files you plan on tweaking or have custom settings for. Most of these with be in ~/.config/ but some will be in ~/ . (ie. mkrc ~/.bashrc for your bash settings and aliases)

Prior to catching the Nix brainworms and switching to home-manager, I mostly used thoughtbot/rcm.

Personally I like (and use) rcm. Everything is still in a git repository, but has more features that work well for sharing across multiple machines.

Check out https://github.com/thoughtbot/rcm

I use rcm. It assumes you keep a separate (potentially version-controlled) folder at ~/.dotfiles or similar, and it provides a suite of tools for managing the symlinks.

https://github.com/thoughtbot/rcm

currently I am managing my dotfiles with rcm (ran by ansible). This approach served me well over the years but recently I stumpled over chezmoi.

Setup a Github/Gitlab account and find a dotfile manager you like (I'm using RCM - it can do more than I actually use it for).

Ansible v2.16

Ansible is a tool used to help manage software automation processes, configuration management across machines, deployment as well as remote execution of commands and scripts. In sports, Ansible operates as the coach of your team by providing strategies (playbooks), and actions, and ensuring the smooth execution of tasks across your infrastructure, just like a coach guides and directs players (Servers)during a game.

They support for-if from python, too: https://jinja.palletsprojects.com/en/3.1.x/templates/#loop-f... but I haven't tried the "recursive" keyword to know if ansible supports that. I say "ansible supports that" because they don't just drop jinja2 into ansible and call it a draw, they have a bunch of custom execution integrations: https://github.com/ansible/ansible/blob/v2.16.3/lib/ansible/...

To manage a VM, you can use something as simple as just manual actions over SSH, or can use tools like Ansible, Hashicorp's Packer and Terraform or other automations. For an app where there is minimal load and security/reliability concern, VMs are still a great option that provide a lot of value for the buck

In this article's context, it is simply a tool that provides a declarative way to automate your machine/OS to configure the development machine as you want (install package, modify the configuration, etc). Examples of these tools are Ansible, Puppet, etc.

Now we're getting more tangential, but for years, Ansible releases were named for Van Halen songs (see old Changelog here: https://github.com/ansible/ansible/blob/v1.8.4/CHANGELOG.md)

In the lab to follow, we'll quickly provision a 3-node kubeadm cluster (1 master, 2 workers) on the cloud provider of your choice using an automation stack comprised of OpenTofu and Ansible, then deploy Rook Ceph using the official Helm charts and confirm that we are now able to successfully create CSI volume snapshots from PVCs by reusing the MinIO example from our last article.

Ansible-Core ↗