I keep most of them in a git repository that I check out at ~/.config. Some software doesn't follow the XDG Base Directory Specification out of the box but can be configured to do so; the Arch Linux wiki has an article about it. For software that cannot be configured to follow the standard I have dedicated repositories, like for OpenSSH.
GNU Stow, backed up to a git repo.
For those who might not see the purpose, it’s for keeping your profiles on different machines in sync, especially if you use the terminal a lot.
Same here.
I don't... when setting up a new system I just copy what I need from any random machine I have logged into at the time. As I need different config for different systems it doesn't really make sense to have one perfect config on all either..
Besides. What is there to really mange. There are only a few that one are likely to change. Every thing else is in /etc. Besides all of thia is in whole system backups and snapshots anyway.
Nix, but I’d only recommend it if you share my same brand of mental illness
I also share this brand of illness.
As I was reluctant going all in, having kept them in git since 2012, I still keep a few of them in their own separate repository. I load them as a nix flake input, and put the files in the expected place using nixos. Works OK, but adds a bit of a roundtrip if you are experimenting with changes often.
This also allows me to share some of them to my work machine, which uses nix, and other files on other systems that dont.
That said, I consider myself all in nix quite some time ago, and have moved more and more of the config over to the nix repo using the nix language for config instead of the input flake config file approach. Iterating on it is much faster this way.
This is the way.
I use Syncthing with a folder called "Configuration Files" where I drop all my sync-able configs and dotfiles and I simply symlink them as needed.
Gnu stow and a git repository.
stow creates bulk symlinks according to the folder structure.
This is what I use and it's been a godsend in my home lab.
chezmoi does everything I need. It's really nice; would recommend.
Chezmoi with auto-push is the way
I don't necessarily sync my dotfiles across machines, at least not in a blanket fashion. But I use Seafile to keep all sorts of directories in sync across machines. It's basically a self-hostable Dropbox.
How many dot files are you changing to need some sort of manager?
For me it’s more about keeping multiple systems in sync and working as intended. E.g. I have my laptop, a home server with couple different distros and a few cloud VMs. Whenever I change a keybind in neovim or tmux or whatever, I just save the changes in a slightly different way and now every machine has those changes so I don’t need to update each machine manually.
I used to have everything in a git repo, but nowadays I use Nix with Home Manager, and I don't want to look back.
Same! I even manage three different configs with the same flake!
Don't need to I use nix
This is how I handle my nix configs though
Love it!!
I use YADM which is a thin wrapper around a bare git repo but still has some creature comforts like per-machine configs and templating.
Since you still need to interact with Git, I pair it with Lazygit. Love that software, I do everything Git with it now!
Unfortunately it is a little jank due to the way Lazygit handles bare repos, thankfully there's a command that sets up the needed Git variables for it to work correctly: yadm enter lazygit
I send the repo to my own Forgejo instance. Kinda overkill but I was already self-hosting other services so I thought "Fully private Git server just for me? Why not?"
Now, this is only for managing user level files. For managing system level configs I haven't setup anything yet.
YADM has a solution for this but it seems a little jank, maybe I'll learn Ansible instead, dunno.
I just wrote a bash script copies the relevant files or directories I want to back up from either ~ or ~/.config and places them in a local git directory which I then push to a private repo on Codeberg. Super janky and manual but I update dotfiles so seldom that it works for what I need.
I use yadm which is basically git repo with automated path handling and alternate files support. I heard that gnu stow is also a good choice, but I haven't tried that
Ok I’m going to look into this one for sure.
I use a bare git repo. After the initial set-up its just the basic git commands but invoked with a gitdf alias. I wrote a (non-monetized) blog post here about it.
If still needing a tui you could write a simple helper script to call the commands.
I'm using stow, and then git for versioning. The only question I'm currently facing is whether to keep my stow packages as individual got repos (so I can switch branches for radically different configs or new setups) or treat the whole lot as a big repo, and set the others up as subtrees.
IMO you shouldn't use branches for switching between configs. It makes it hard to compose and reuse your configuration.
Just imagine you have a new config file that you now want to add to all of your machines. You'd now have to commit/cherry-pick on all of your branches. Change that file? Now you have to distribute the changes again and might even get conflicts.
Additionally, many programs allow you to change your configuration directory via environment variables (usually XDG_CONFIG_HOME , I think).
So you can even keep all machine-specifig configuration files in a single repo under different prefixes for those.
I use home-manager to manage most of my dotfiles and store them in a git repository. Additionally, I just symlink the configurations I'm too lazy to write as home-manager options (yet), which in turn is a decent way to make migrating to home-manager options less upfront.
I do manage them via git. But I only do it so have settings (and their changes) synchonised between 2 PCs and a laptop.
With just one main device I don't even see a reason to "manage" anything... a basic backup strategy completely independent of just dotfiles aside.
Chezmoi
It’s the only one that just works and has enough features for me, but not too many.
I'm using VCSH, which allows me to split the home directory into multiple git repos without worrying about symlink consistency (like with GNU stow) or apps that have problems with symlinks.
The syntax is exactly the same as git, only that I do (for example) vcsh emacs add -p instead of git add -p.
I do a git repo for my dot files with an installer that configures it based on whether I’m using Linux, macOS, or FreeBSD; a server or desktop; and whether I’m in bash or zsh. It also includes a bunch of functions and aliases that I find useful. It’s not always pretty because I also use it as a practical place to try new shell script bits when I have time. I’m hoping to change some things around soon thanks to some ideas from Dave Eddy’s bash course at ysap.sh.
i used to do this, but couldn't figure out how to stay on top of the changes introduced by distro's and updates to the apps; did you figure these out somehow?
I pretty much stick to straight bash and core utils, so it’s not much of a burden. Plus on the Linux side, I mostly stay with Debian and its derivatives, which limits some of the work.
But really I don’t consider every feature of my dot files to be a finished product. The core stuff is reliable, but if I catch a problem with anything more esoteric or if I see some functionality that looks interesting, it’s a brain teaser I get to tackle.
bash isn’t standard on most systems.
I keep them in a Fossil repository (with a few private log-in data stored in a SyncThing folder instead) and I just ln them where I need them.
Nothing at all. If things go south on the install I'll have a clean slate. Really the only thing I have backed up are keys, everything else is nonessential.
Nix (home-manager) 😬
I created a file tree that looks similar to my system's file tree, except it only contains all the files that I modified or added and only their respective directories. From there I just use rsync to sync those files/file tree to the system's /.
It's convenient to see what changes I currently have but it requires a bit of manual maintenance. I only really started doing it that way because I was learning how to use rsync and I just kept going on with it because it was working for me.
I'm only working with my laptop, android phone and two Raspberry Pi's so I can get with my little rsync based setup.
I use stow and it does the job get nicely, but it's possible that there's a better option these days
I push them to Git, secrets are masked with Mozilla SOPS.
Git + Guix Home
Don't think too hard on it. Just use git. For example, I have a repo called handy-scripts that hosts all my dotfiles. I just check that out into ${HOME}/projects/handy-scipts and then symlink everything from where it's expected to its corresponding place in the repo.
As you make modifications, remember to occasionally do a git pull --rebase && git commit -m WIP && git push so that all your devices are synced up.
I never did until I started using hyprland.
Now I have those in a git repo: https://git.jeena.net/jeena/hypr-dotfiles
I don't understand what to manage about dotfiles. You mean backups?
It doesn't have to be a big baroque thing. When there's a dotfile I configure regularly, I move it to a Git repo and use stow to put it "back" into place with a symlink. On new machines, it isn't long before I try something that doesn't work or see the default shell prompt and go "oh yeah, I want my dotfiles", check out the repo, run a script that initializes a few things (some stuff is machine-specific so the script makes files for that stuff with helpful comments for me to remember the differences between login shells or whatever) and then I'm off to the races.
So its more a general question how to backup (with versioning) these files. I just always wondered what "manage" in this context meant. I don't handle them differently than any other file to backup.
Dazed and confused.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0