Gnu stow and a git repository.

stow creates bulk symlinks according to the folder structure.

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..

Nix, but I’d only recommend it if you share my same brand of mental illness

chezmoi does everything I need. It's really nice; would recommend.

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.

How many dot files are you changing to need some sort of manager?

Don't need to I use nix

This is how I handle my nix configs though

https://github.com/Givlucas/nixos

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.

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

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.

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 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 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.

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.

Chezmoi

It’s the only one that just works and has enough features for me, but not too many.

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 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.

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 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.

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 push them to Git, secrets are masked with Mozilla SOPS.

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.

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.

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.

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.

I never did until I started using hyprland.

Now I have those in a git repo: https://git.jeena.net/jeena/hypr-dotfiles

For ZSH, I have a script that automatically installs oh-my-zsh and a bunch of zsh plugins, and changes my default shell to ZSH.

For everything else, some files will just get copied over, others left behind. I only "manage" them when I need to view/edit them.

Neovim and scp. I should clearly test some things.

Git repo that I sync with my raspberry pi. You never know if some of the dotfiles contain sensitive info so I like to keep them on machines that only I can access

Heard about this on Linux Unplugged a few weeks back. Haven't had a chance to test it out yet, but it looks pretty cool.

https://flathub.org/en/apps/com.ml4w.dotfilesinstaller

https://github.com/thoughtbot/rcm once upon a time, but I haven't really had multiple dev computers for a while

I don't understand what to manage about dotfiles. You mean backups?

Dazed and confused.

Recently learned about dotbot and it is perfect for me. Had a custom script to manage stow before.