@codeviking's dotfiles

This repository captures what's required to configure my development environment.

Prerequisites

Before getting started, install brew.

Usage

To setup a new environment:

git clone git@github.com:codeviking/dotfiles.git

# Install minimum dependencies.
./bootstrap.sh

# Install common packages.
./install.sh

# Add fish as a shell candidate by editing `/etc/shells`:
sudo echo "$(brew --prefix)/bin/fish" >> /etc/shells

# Change the default shell to fish.
chsh -s "$(brew --prefix)/bin/fish"

Once that's complete launch a new terminal. Run link.sh to finalize things:

# Link configuration files into expected locations.
./link.sh

# Configure oh-my-fish (https://github.com/oh-my-fish/oh-my-fish)
./omf.sh

# Configure git
./gitconf.sh

You should now see something like this whenever you start a new terminal:

There's one more step to get things running. Launch nvim and dismiss the error about a missing theme. Then run :PackerSync to install the configured list of nvim plugins (which includes the theme).

That's it. You're all set!

Advanced

Commit Signing

I use gpg to sign commits. This repository includes scripts for setting that up.

First, follow these instructions for generating a new key and adding it to GitHub.

Next initialize things locally by running:

./gpg.sh

And finally follow these steps for telling git about your signing key.

Host Specific PATH Extensions

As much as we'd like to avoid it, host-specific $PATH extensions are at times warranted.

To set host specific $PATH extensions create a file at the path $HOME/.config/paths.fish that looks something like this:

#!/bin/fish

# gcloud
source "$HOME/lib/google-cloud-sdk/paths.fish.inc"

fish_add_path "$PATH:$HOME/bin"

The commands above are examples, populate the file with the $PATH specific changes that make sense for the host you're on.

codeviking / dotfiles