Skip to content

Latest commit

 

History

History
131 lines (89 loc) · 5.59 KB

README.md

File metadata and controls

131 lines (89 loc) · 5.59 KB
Raw

Instructions for Fullstack Academy Students

  1. Fork this repo
  2. git clone the forked repo on to your local machine
  3. Go through each setting in the .osx file and comment out the settings you don't want to apply (or uncomment the ones you want). In general, if a setting doesn't make sense to you, probably best to comment it out.
  4. type ./.osx in your terminal to apply all these settings (you will have to restart after doing this)
  5. Copy the .aliases file to your home directory using command: cp .aliases ~
  6. Add the line: source .aliases to your ~/.bashrc OR ~/.bash_profile file.
  7. Look through the aliases file to learn the new aliases that you can use on your terminal and Feel the Power!

Raise your hand if you have questions.

The original instructions of this repo are below, you DO NOT need to follow the Installation instructions outlined below.


--

Mathias’s dotfiles

Installation

Using Git and the bootstrap script

You can clone the repository wherever you want. (I like to keep it in ~/Projects/dotfiles, with ~/dotfiles as a symlink.) The bootstrapper script will pull in the latest version and copy the files to your home folder.

git clone https://github.com/mathiasbynens/dotfiles.git && cd dotfiles && source bootstrap.sh

To update, cd into your local dotfiles repository and then:

source bootstrap.sh

Alternatively, to update while avoiding the confirmation prompt:

set -- -f; source bootstrap.sh

Git-free install

To install these dotfiles without Git:

cd; curl -#L https://github.com/mathiasbynens/dotfiles/tarball/master | tar -xzv --strip-components 1 --exclude={README.md,bootstrap.sh,LICENSE-MIT.txt}

To update later on, just run that command again.

Specify the $PATH

If ~/.path exists, it will be sourced along with the other files, before any feature testing (such as detecting which version of ls is being used) takes place.

Here’s an example ~/.path file that adds ~/utils to the $PATH:

export PATH="$HOME/utils:$PATH"

Add custom commands without creating a new fork

If ~/.extra exists, it will be sourced along with the other files. You can use this to add a few custom commands without the need to fork this entire repository, or to add commands you don’t want to commit to a public repository.

My ~/.extra looks something like this:

# Git credentials
# Not in the repository, to prevent people from accidentally committing under my name
GIT_AUTHOR_NAME="Mathias Bynens"
GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME"
git config --global user.name "$GIT_AUTHOR_NAME"
GIT_AUTHOR_EMAIL="[email protected]"
GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"
git config --global user.email "$GIT_AUTHOR_EMAIL"

You could also use ~/.extra to override settings, functions and aliases from my dotfiles repository. It’s probably better to fork this repository instead, though.

Sensible OS X defaults

When setting up a new Mac, you may want to set some sensible OS X defaults:

./.osx

Install Homebrew formulae

When setting up a new Mac, you may want to install some common Homebrew formulae (after installing Homebrew, of course):

brew bundle ~/Brewfile

Install native apps with brew cask

You could also install native apps with brew cask:

./.cask

Feedback

Suggestions/improvements welcome!

Author

twitter/mathias
Mathias Bynens

Thanks to…