Open kalkayan opened 3 years ago
@kalkayan
Been trying to read the article series referenced on your github link you posted. But there's only part 1 and part 3 up on your site - would love to see part 2 to understand how you're doing the brew stuff
Manging dotfiles using symlink has been like a tradition and almost all the developers are doing it, if not having multiple copies of there dotfiles . But there exists a much better way - people at atlassian has written a very nice article about it using the git's
--bare
feature and using it to store the dotfiles and I have to say this, it very elegant. The trick to managing these dotfiles is by creating a bare git repository.The reason for this Issue is to make people aware about way and this repository is the best place for it, cause lets face it every developer trying to customize there os has or will peek into this repo atleast once.
Managing and tracking [dot]files with bare repo
I'm copy pasting it from https://github.com/kalkayan/dotfiles
Clone the repo as a bare repository and thats it! no problems related to symlinks.
Now next step is to checkout to the proper branch according to the os of the machine.
Usage of dotfiles
This method of managing and sharing has various advantages some of them are shown below:
1. Keep the dofitles versioned, (basically all the cons of using git) At this point, all your configuration files are being tracked, and you can easily use the
dotfiles
command (see this line in .aliases) to manage the repository, some examples are:-2. Share on Multiple devices Share the same configs of multiple devices with minimal changes using
branch
, create a branch for your new machine, example:-3. Create Profiles for dotfiles Create configs based on your environment using
branch
, create a branch and configure according to you work env.@mathiasbynens