Dotfiles

This repository will let you generate symlinks for your bash profile and link in dotfiles for us by various utilities. The linking script is written to generate symlinks for shell commands and dotfiles you want under version control.

The repository is premised under the use of a .bash_profile that sources all dotfiles in a directory (defaulting to .dfsrc). All other files put under link/ will be symlinked to your $HOME directory, maintaining their path. This allows you to customize or bring under version control only certain files that may be part of a larger package installation (a good example of this is the .atom directory in this repo).

The link-links.sh script will crawl your link/ directory and symlink all of the files individually, maintaining their path. Big thank you to @janmosen for motivation in writing the linking library.

Quick setup

chmod +x link-links.sh
./link-links.sh --dry-run
./link-links.sh

This will symlink all links in the /link directory to your $HOME directory.

Bootstrapping a new PC

bootstrap.sh

This file provides a way of installing static dependencies for a new machine. It is customized for my machine, but provides an easy templates for easily modifying things. There are some example commands of:

1. installing homebrew packages
2. installing atom packages
3. setting up a sane directory structure
4. some nice osx modifications courtesy of @mathiasbynens
5. setting up docker for you
6. installing nvm for Node JS development

Multi-ssh configuration

a .sshprofiles directory in link/ can be combined with set-<identity> commands to switch between different ssh keys and config files. You can see an example of how these bash commands work below. Along with corresponding keys and ssh config files this can be a quick and neat identity management system. Be warned that this assumes a dynamic ~/.ssh directory and will delete any keys you may have currently existing there.

Note: A private repository that utilizes the link-links script can be a quite effective way of managing this. Keeping private bash commands and keys separate. Just chmod 400 your private key symlinks so that ssh is okay with doing this.

set-identity example

Careful using this!!

dotfiles-private/link/.dfsrc/.sshaliases

set-riguy724() {
  export SSH_PROFILE_NAME=riguy724
  set-ssh
}

set-ssh() {
  rm -rf ~/.ssh
  ln -fs ~/.sshprofiles/$SSH_PROFILE_NAME ~/.ssh
}

dotfiles-private/link/.sshprofiles

• riguy724
  • config

    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null
    
    Host riguy724-bastion
        User riguy724
        Hostname example.com
        Port 22
    
    Host server1
        User ubuntu
        Hostname server1.example.com
        Port 22
        ProxyCommand ssh -W %h:%p riguy724-bastion
    

  • id_rsa
  • id_rsa.pub

After running link-links.sh from your private repository you'll have to update your private keys permissions to make it usable:

chmod 400 dotfiles-private/link/.sshprofile/riguy724/id_rsa

Use the alias:

set-riguy724

You should be all set... ssh away!