#Dotbot shell how to#
#Dotbot shell install#
#Dotbot shell update#
#Dotbot shell full#

When writing nested constructs, keep in mind that YAML is whitespace-sensitive.įollowing the formatting used in the examples is a good idea. Tasks are run in the order in which they are specified. Is a dictionary that contains a command name mapping to data for that command. Updates between machines becomes really easy).ĭotbot configuration files are arrays of tasks, where each task This makes a lot of things easier to do (in particular, syncing Installer should be able to be run multiple times without causing any Ideally, bootstrap configurations should be idempotent.

#Dotbot shell how to#

Currently, Dotbot knows how to link files andįolders, create folders, execute shell commands, andĬlean directories of broken symbolic links. Configurationĭotbot uses YAML or JSON-formatted configuration files to let you specify how JSON configuration files areĬonventionally named. The configuration file is typically written in YAML, but it can also be written defaults : link : relink : true - clean : - link : ~/.nf : nf ~/.vim : vim ~/.vimrc : vimrc - create : - ~/downloads - ~/.vim/undo-history - shell :. The conventional name for the configuration file is. Here's an example of a complete configuration.

#Dotbot shell install#

If you prefer, you can install Dotbot from PyPI and call it as a command-line Subrepo, run git fetch & git checkout origin/master in the Dotbot directory. The old version of Dotbot will be checked out by the install script. Submodule be sure to commit your changes before running.

#Dotbot shell update#

If using a submodule, run git submodule update -remote dotbot, substituting dotbot with the path to the Dotbot Setting up Dotbot as a submodule or subrepo locks it on the current version. You can change either of these parameters byĮditing the variables in the install script appropriately. By default, the scriptĪssumes that the configuration is located in the Dotbot

#Dotbot shell full#

Version of Dotbot and calls the full Dotbot installer. Note: The install script is merely a shim that checks out the appropriate To help you get started we have anĮxample config file as well as configurationĭocumentation for the accepted parameters. To get started, you just need to fill in the and Dotbot If you are using PowerShell instead of a POSIX shell, you can use the provided Hg init # initialize repository if needed echo 'dotbot = ' >.

If you're using Mercurial, you can add Dotbot as a subrepo: cd ~/.dotfiles # replace with the path to your dotfiles gitmodules dirty # ignore dirty commits in the submodule Git init # initialize repository if needed If you're using Git, you can add Dotbot as a submodule: cd ~/.dotfiles # replace with the path to your dotfiles The following will help you get set up using Dotbot in just a few steps. You're just looking for some inspiration, we've got you covered. Template repository, check out dotfiles_template. Great! You can automate the creation of your dotfiles by using the Replacement for any other tool you were using to manage your dotfiles, andĭotbot is VCS-agnostic - it doesn't make any attempt to manage your dotfiles.Įxplanations of how to organize your dotfiles. It does less than you think, because versionĭotbot is designed to be lightweight and self-contained, with no externalĭependencies and no installation required. Directives ( Link, Create, Shell, Clean, Defaults)ĭotbot is a tool that bootstraps your dotfiles (it's a files.install, even on a freshly installed system! Dotbot makes installing your dotfiles as easy as git clone $url & cd dotfiles &.