Your dotfiles are how you personalize your system. These are mine.
This setup prioritizes keeping files short and organized by separating things into topic-specific folders (i.e. Git setup.sh, git config, git ignore, and git aliases all go in the git/ folder).
Run this:
git clone https://github.com/lkgarrison/dotfiles.git ~/.dotfiles
cd ~/.dotfiles
script/bootstrap
This will symlink the appropriate files in .dotfiles
to your home directory.
Everything is configured and tweaked within ~/.dotfiles
.
Everything's built around topic areas. If you're adding a new area to your
forked dotfiles — say, "Java" — you can simply add a java
directory and put
files in there. Anything with an extension of .bash
will get automatically
included into your shell. Anything with an extension of .symlink
will get
symlinked without extension into $HOME
when you run script/bootstrap
.
A lot of stuff. Check thing out with the file browser above and see what components may mesh up with you. Fork it, remove what you don't use, and build on what you do use.
There's a few special files in the hierarchy.
- bin/: Anything in
bin/
will get added to your$PATH
and be made available everywhere. - topic/*.bash: Any files ending in
.bash
get loaded into your environment (i.e. aliases.bash, completion.bash, etc). - topic/*.symlink: Any files ending in
*.symlink
get symlinked into your$HOME
. This is so you can keep all of your dotfiles versioned in your dotfiles repo but still keep them easily accessible in your home directory. These get symlinked in when you runscript/bootstrap
.
I forked my dotfiles setup from https://github.com/holman/dotfiles