DOTBOT SFV HOW TO
DOTBOT SFV INSTALL
DOTBOT SFV MANUAL

Maybe dotbot could detect new dotfiles and help you automate moving them to your dotfiles repository and setting up links.īasically all sorts of smart/interactive things would be nice additions and would bring more to the table than long discussions about favorite configuration format that people agree with your thoughts on YAML vs a DSL vs the Lisp-like syntax. Users who want to fully automate everything should have a way to disable interactive execution. Like ask user what to do if file is already there.

DOTBOT SFV MANUAL

It would be nice if dotbot provided manual actions with smart options.

DOTBOT SFV INSTALL

Supporting multiple configuration languages is nice as long as it doesn't take too much time away from the main focus of the project.Īs for me I think the install update process could be better. The language should be something popular and not too verbose.

Secondly it would just be another thing for the end-user to learn.

First of all it's overkill for something like this. If you want full blown logic you could just write everything in bash or any scripting language yourself and not use dotbot.Ĭreating new config language in my opinion is not a good idea. Logic in config files would be nice but I think there are only few cases where you would want it. You clone/pull the repo and you're ready to install or update. This issue will be used for discussing the design of v2.0.) (This top post will be edited as stuff happens. Should it be on the master branch? Should Dotbot 2.0 forever live in a 2.0 branch with master being reserved for bugfixes for 1.0?

DOTBOT SFV HOW TO

Because people use Dotbot as a submodule, we need to be careful when figuring out how to ship the upgrade.Maybe there are other completely different ways to do it too. What file format do we want to use? There are a couple options I can think of: JSON/YAML file (declarative), other data format (e.g.

Make Dotbot usable as a Python library (see Make Dotbot usable as a Python library #75).Support interactive execution (see Support interactive execution #74).Automatic backup / replacement of dotfiles (see Backup #12 and Replace with backup #36).Uninstall command to delete symlinks specified in install config (see suggestion of new features #49, 4th item).Be able to write to files/folders that require special privileges (see suggestion of new features #49, 3rd item).Platform specific link paths (see Platform specific link paths #57).CLI flag to only run certain sections (see CLI flag to only run certain sections? #44 and suggestion of new features #49, 2nd item).Backup (see make a back up of overwiritten file or folder #90).Improved error messages (see Improve error messages #73).Default options (see force - does it overwrite any file? #34 and Add default options #77).Directive plugins (see Directive Plugins #65).We'll only switch to the name 'v2.0' if/when we decide to add features that are not backwards compatible. All features that are backwards compatible are being included in Dotbot v1.0 as they are added. This issue is meant for tracking work on Dotbot v2.0, the first major release since v1.0 in March 2014.

Dotbot sfv