A smarter deploy script about dotfiles

[maxg203]

My dotfiles are really minimal in comparison to these but one of my favourite things about mine is the way I install it. I copy four lines, one of which clones the git repo as a bare repository and one runs an install script which gets Vundle and runs :PluginInstall for me. The repo is stored under ~/.cfg and I use an alias like alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME' in place of the git command to manage the dotfiles Git repo from any directory. I use this install method with Mac and Linux and have had no issues. I would recommend it.

My dotfiles README.md also has a link to the Atlassian article that gave me the core idea for this.

[Parth]

This is what I ended up coming across with., what do you think @maxg203? Now all I have to do is clone parth/dotfiles and ./deploy. I took a look at your dotfiles, the main thing my ./deploy does is source all my dotfiles. This way, the dotfiles can keep themselves upto date.

[maxg203]

Very nice. I might add something similar, I love the OS independent if logic for installing system packages on lines 9-19. I've been wanting to add this sort of thing to install neovim by default alongside vim (have you seen nvim)? Also, optionally saving old files is a nice to have - though I doubt you'll ever need to say yes (line 82). Personally I think I might do separate install/update scripts. Thanks for highlighting to me that my post-installation dotfiles management needs a script!

[maxg203]

My super hacky deploy solution... maxg203/dotfiles@258ac06 (install is still seperate).

[Parth]

Very nice, have also been thinking about #39. Maybe it would be better to depend on dependency management repositories like apt and brew.