4 ms·

No need to over complicate things. I just have my ~/.dotfiles and if I remembered I saved a list of installed packages on my old install that I can go through a

by towb 7y ago

No need to over complicate things. I just have my ~/.dotfiles and if I remembered I saved a list of installed packages on my old install that I can go through and pick whatever I need. Could add some scripts for the things I know I need to do but that's already adding too much. My feeling is you'll end up working hours and hours to create the perfect setup (which doesn't exist so you just keep tweaking it forever).

e12e 7y ago
I've got home in a git repo with an on commit trigger to push to a remote repo. There's some conveniences in my bashrc (add ~bin to PATH, add bash completions from ~/.bash_completions, similar for man-path etc). Vimplug handles my (neo)vim plug-ins, so I just have a short .vimrc-file. I've recently consolidated on asdf as a version manager for my workstation, so I no longer manually muck with ruby/python/go venv/paths: https://asdf-vm.com/#/ https://asdf-vm.com/#/
stevekemp 7y ago
If you remember you export the list of packages? That sounds very manual, and prone to failures. I'm surprised people in this thread aren't talking about backups. I have my dotfiles stored under revision-control, like many others here. I have a couple of notes about the setup of each host I store too. But basically I install Debian packages and that's 99% of the my install. The only stuff that I install, outside my own code, are things like the ARduino IDE, Firefox, Calibre, and they get installed beneath /opt Despite the lack of "real" state I still take a backup every day, and that has saved me more than once.
- towb 7y ago
  Woops! Late answer. ~/ is backed up nightly and ~/.dotfiles is on github, have some other configs on there too that I don't keep in .dotfiles, not that it matters. The remember part is just that it doesn't really do any difference in the end, I will install what I need when I need it anyway, the important part is to keep the config that I have spent hours and days making mine. :)

by towb 7y ago

e12e 7y ago

I've got home in a git repo with an on commit trigger to push to a remote repo. There's some conveniences in my bashrc (add ~bin to PATH, add bash completions from ~/.bash_completions, similar for man-path etc). Vimplug handles my (neo)vim plug-ins, so I just have a short .vimrc-file. I've recently consolidated on asdf as a version manager for my workstation, so I no longer manually muck with ruby/python/go venv/paths: https://asdf-vm.com/#/ https://asdf-vm.com/#/

stevekemp 7y ago

If you remember you export the list of packages? That sounds very manual, and prone to failures. I'm surprised people in this thread aren't talking about backups. I have my dotfiles stored under revision-control, like many others here. I have a couple of notes about the setup of each host I store too. But basically I install Debian packages and that's 99% of the my install. The only stuff that I install, outside my own code, are things like the ARduino IDE, Firefox, Calibre, and they get installed beneath /opt Despite the lack of "real" state I still take a backup every day, and that has saved me more than once.

towb 7y ago
Woops! Late answer. ~/ is backed up nightly and ~/.dotfiles is on github, have some other configs on there too that I don't keep in .dotfiles, not that it matters. The remember part is just that it doesn't really do any difference in the end, I will install what I need when I need it anyway, the important part is to keep the config that I have spent hours and days making mine. :)