Thread replies: 5
Thread images: 1
Thread images: 1
File: how to be black.jpg (48KB, 500x667px) Image search:
[Google]
48KB, 500x667px
Hey /g/, how do you document your shit?
Like say you had to reinstall your main machine right now. (malware infection, drive death, whatever) How do you keep track of what you'd need to set up again on it? Software to be installed, how its to be configured, and so on. Yeah some of it you can just back up dotfiles in your home directory, but some stuff is either too big of a clusterfuck (GNOME/GTK stuff, Firefox configuration/profiles), or it doesn't live there (e.g., I'd have to set up Samba, ZFS on Linux, fuck around with some things in sshd_config, etc) And I'm sure some of you have fancy riced-out themes and shit. I don't even want to think about the shit I'd have to do to rebuild the Win7 machine I use for vidya.
So how do you keep track of it? Right now I just have a folder full of saved configs and checklists for where to put them and settings I need to change, wondering if there's some better way to do this that I'm missing.
>>
>>62260500
If text files, configs etc, I just use git. Otherwise I keep the installer for software I've downloaded as a record
>>
Keeping your home folder in a separate partition while backing it up monthly (while also keeping timeshift backups) has worked fine for me so far, i was surprised when i switched from debian to arch and all my firefox plugins were already installed my telegram was also still logged in (after i installed it again).
>>
I use Chef and Puppet. My old job I I used Chef so my desktop Linux stuff is mostly in Chef still. My home servers are all managed by Puppet I use Puppet at my current job. Go with Chef.
>>
>>62260500
>keep track of what you'd need
I don't.
I just mirror my entire drive every once in a while.
Thread posts: 5
Thread images: 1
Thread images: 1