13 stable releases (3 major)

3.1.0 May 11, 2022
3.0.0 Feb 23, 2022
2.2.4 Feb 19, 2022
2.2.3 Dec 30, 2021
0.1.0 Aug 5, 2020

#402 in Development tools

Download history 4/week @ 2022-04-20 120/week @ 2022-04-27 87/week @ 2022-05-04 235/week @ 2022-05-11 60/week @ 2022-05-18 57/week @ 2022-05-25 113/week @ 2022-06-01 32/week @ 2022-06-08 6/week @ 2022-06-15 9/week @ 2022-06-22 20/week @ 2022-06-29 2/week @ 2022-07-06 16/week @ 2022-07-13 29/week @ 2022-07-20 45/week @ 2022-07-27 31/week @ 2022-08-03

121 downloads per month

MIT and CC-PDDC licenses

5.5MB
25K SLoC

JavaScript 20K SLoC // 0.1% comments Rust 2K SLoC // 0.0% comments BASH 1.5K SLoC // 0.5% comments Shell 337 SLoC // 0.1% comments RPM Specfile 41 SLoC Batch 26 SLoC Python 22 SLoC // 0.6% comments Objective-C 1 SLoC

Toml Bombadil - A dotfile manager written in rust

GitHub Actions workflow status Code coverage status AUR package
crates Conventional commits Repository license

Documentation · Installation · Configuration

A dotfile manager written in Rust

  • Dotfile template: define your dotfiles templates and link them as needed.
  • Dotfile profiles: create profiles for different machines and situations and combine them on the flow.
  • Installation hooks: run custom commands before and after installing your dotfiles.
  • Gpg encryption: add encrypted secrets to your dotfile configuration with gpg.

Explore Toml Bombadil's docs  ▶

example gif

Why another dotfile manager ?

I wrote Toml Bombadil because I kept changing my desktop environment: switching from i3 to sway, from sway to xfce, from xfce to gnome and back to sway. When you keep changing your working environment like this you end up with several problems:

  • Some symlinks will end up orphans.
  • Not every program you use support Xresources and you will most probably have to manually edit some themes/config.
  • When starting a fresh installation you will very likely need to adapt your existing dotfiles to your new machine.
  • It is a mess.

Toml Bombadil try to solve this with a simple addition to the symlink method used by other tools: instead of creating a symlink from a dotfile to the actual config path of a program, it will create a copy of it and symlink the copy. This additional step allow to use your original dotfile as a template and inject variables in the copy. You can have multiple value files in the same dotfile repository and change color scheme, or any value on the fly.

In addition, this is completely optional, you could start using Toml Bombadil only to generate symlinks and templatize your dot file progressively.

Installation

Arch Linux:

pacman -S toml-bombadil

Cargo:

cargo install toml-bombadil

Quickstart

See Docs -> Quickstart.

Shell completions

Command line completion scripts for several popular shells can be generated by running bombadil generate-completions. An example for generating a completion script and outputting it to a file for zsh would be bombadil generate-completions zsh > <somewhere on your $fpath>/_bombadil. Available shells are: bash, elvish, fish, and zsh.

Troubleshooting

If you get lost you can use bombadil get {resource_name} to see what is currently configured. Available resources are dots, hooks, path, profiles, vars, secrets.

Optionally you can display resources for a profile with the --profiles flag.

Example repositories

If you use Bombadil please submit an issue, or a PR to update this section, we will be happy to reference your dotfiles here!

Contributing

Found a bug, have a suggestion for a new feature? Please read the contribution guideline and submit an issue.

License

All the code in this repository is released under the MIT License, for more information take a look at the LICENSE file.

Dependencies

~21–29MB
~623K SLoC