All Projects β†’ jacobwgillespie β†’ dotfiles

jacobwgillespie / dotfiles

Licence: MIT license
🏠 dotfile configuration for macOS and Linux

Programming Languages

shell
77523 projects
ruby
36898 projects - #4 most used programming language

Projects that are alternatives of or similar to dotfiles

Jarvis
Dotfiles for a powerful, web development-focused environment powered by Neovim, iTerm2, tmux, and zsh
Stars: ✭ 617 (+1567.57%)
Mutual labels:  zsh, homebrew
dotfiles-legacy
. .✧ Β· 🌎 ✷ ✫ πŸŒ™ Β· ✡ πŸš€βœ΅ * ✡ Β· 🌌✫ ✷ Β· ✧ .
Stars: ✭ 15 (-59.46%)
Mutual labels:  zsh, homebrew
Dotfiles
vim, zsh, git, homebrew, nvm, neovim - my whole world
Stars: ✭ 2,217 (+5891.89%)
Mutual labels:  zsh, homebrew
dotfiles
🏠 dotfiles for my macOS environment
Stars: ✭ 17 (-54.05%)
Mutual labels:  zsh, homebrew
Dotfiles
Get started with your own dotfiles.
Stars: ✭ 1,094 (+2856.76%)
Mutual labels:  zsh, homebrew
Dotfiles
πŸ’» Use command line interface manager for macOS configuration.
Stars: ✭ 97 (+162.16%)
Mutual labels:  zsh, homebrew
Dotfiles
🌷
Stars: ✭ 209 (+464.86%)
Mutual labels:  zsh, homebrew
brewfile
🍎 Brewfile to install softwares in macOS for engineers
Stars: ✭ 37 (+0%)
Mutual labels:  homebrew
homebrew-essentia
Homebrew build scripts for Essentia
Stars: ✭ 25 (-32.43%)
Mutual labels:  homebrew
ym2017
A music album for the Sega Mega Drive
Stars: ✭ 17 (-54.05%)
Mutual labels:  homebrew
ibrew
🍻Interactive CLI for Homebrew – the missing package manager for macOS.
Stars: ✭ 33 (-10.81%)
Mutual labels:  homebrew
dotfiles
πŸ—Ώ dotfilery, configuration, environment settings, automation, etc. πŸ›–
Stars: ✭ 67 (+81.08%)
Mutual labels:  homebrew
homebrew-openni2
OpenNI2-related formulae for the Homebrew package manager
Stars: ✭ 41 (+10.81%)
Mutual labels:  homebrew
rombundler
A tiny libretro frontend to release homebrews as executables
Stars: ✭ 49 (+32.43%)
Mutual labels:  homebrew
zsh-config
Faster and enjoyable ZSH (maybe) !!!
Stars: ✭ 64 (+72.97%)
Mutual labels:  zsh
Brewfile.vim
Brewfile syntax for Vim
Stars: ✭ 14 (-62.16%)
Mutual labels:  homebrew
nvm-auto-use.zsh
ZSH plugin to call `nvm use` automatically whenever you enter a directory that contains an `.nvmrc` file with a string telling nvm which node to use
Stars: ✭ 16 (-56.76%)
Mutual labels:  zsh
msfvenom-zsh-completion
zsh completion for msfvenom in Metasploit
Stars: ✭ 42 (+13.51%)
Mutual labels:  zsh
homebrew-devops
🍺 DevOps / SRE formulae for the @Homebrew package manager.
Stars: ✭ 36 (-2.7%)
Mutual labels:  homebrew
homebrew-sass
A Homebrew tap for Sass
Stars: ✭ 22 (-40.54%)
Mutual labels:  homebrew

dotfiles

Dotfiles for configuring macOS or Linux with ZSH and Homebrew.

Requirements

  • macOS or Linux
  • ZSH (on macOS, the install script will install ZSH via Homebrew)
  • Homebrew (on macOS, the install script will install Homebrew)

Installation

$ git clone https://github.com/jacobwgillespie/dotfiles.git ~/.dotfiles
$ cd ~/.dotfiles
$ ./setup

This will install all required dotfiles in your home directory as symlinks. Everything is then configured via modifying files in ~/.dotfiles.

Software

The Brewfile installs all of the software and applications I have installed on my Mac, including Homebrew formulae, Homebrew casks, and Mac App Store applications.

Structure

The repository is organized as follows:

  • setup - setup script that can be used to install or update the dotfiles on your system
  • Brewfile - a list of software to install via Homebrew (see brew bundle and brew bundle cleanup)
  • bin/* - any executable scripts in this directory are added to your $PATH
  • config/*.zsh - configuration files for ZSH, they are all sourced automatically into any new shell
  • functions/* - zsh functions and autocomplete completion definitions
  • symlinks/* - any files ending in *.symlink get symlinked by the ./setup script into your home directory with the suffix removed (e.g. gitignore.symlink becomes ~/.gitignore)

License

MIT License. See LICENSE.

Inspiration

The following repositories served as inspiration for this repository:

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].