So, I just found out about a programme called SynthShell which kind of does the work for you and gives you a nice looking shell, the thing is that this also creates some config files and other stuff in my system, instead of just one .bashrc file to edit. What would be the best way to learn to have a nice looking bash where I can just have a backup of it that I can use throughout systems?
I’ve only started using yadm recently so I may not be able to elaborate in detail, but for me the main draw for using yadm (as opposed to Ansible, which I use at work) is the simplicity. It’s basically just a bash script that uses git, so there’s no dependencies besides git and tools installed on most Unix systems. Ansible felt like overkill for what I needed, ie just something to manage and sync my dotfiles.
Also, maybe it’s personal bias, but I really hate installing/using Python-based programs - they often tend to go wild with their dependencies and eventually break. I recall trying to install Ansible on a Raspberry Pi at some point (via pip) and it failed because one of the dependencies couldn’t be compiled for whatever reason. I gave up after trying to fix it for a while, and dropped the idea. I’ve had similar experiences with other large Python projects, there’s always some drama. Why is why I prefer compiled binaries or simple shell scripts like yadm.
I’ve no issues using Ansible at work though. We use it on RHEL so it’s quite stable and doesn’t have the dependency issues you’d get on a bleeding-edge, ever-changing, end-user system. Plus it really shines at the Infrastructure as Code stuff so we use it to automate everything from networking gear to VMs. But I feel it’s overkill for something as simple as syncing a bunch of text files.
I recently started uses dotbot for managing dot files across my systems. It sounds very similar, in terms of the simplicity of the implementation, to yadm. You define a config file in yaml or json and run the “install” script which calls the dotbot utility, passing in your config file. With a simple change to the install script, I’ve been able to create multiple config files, one per environment (work, home, linux, mac, etc.) and I’ve been thinking about how I could automatically sync changes to git whenever I edit a config file. Leaning towards setting up an autocmd in neovim to automatically commit and push changes on save when I have one of the config files open. Just not yet sure how to do this in a way that would only run the sync for the configs and not every json or yaml file on my system. I’ve only ever set up autocmds for specific file extensions but the syntax leads me to believe it’s flexible enough that any arbitrarily specific file name or path could work the same.