This is better, yes?
This tool is ridiculously early in its development. I'm building out features as I migrate my dotfiles over.
Those dotfiles can be used as a "reference" for migrating your own.
Only for early adopters and masochists.
Comtrya is a tool to help provision a fresh OS with the packages and configuration (dotfiles) you need to become productive again.
I'm a serial OS installer, I wipe the OS on my machines every, approx, 30 days. I've primarily relied on SaltStack to automate this, but I've grown frustrated with the mismatch between configuration management and personal provisioning.
I've also tried Ansible, Chef, Puppet, mgmt, and probably anything else you're about to suggest; they all have a flaw that makes it too cumbersome to adopt for the trivial use-case.
No binaries are distributed yet, please install and build with Cargo.
- HomeBrew installed -> Install Homebrew
- Rust installed ->
brew install rust
cargo install comtrya
comtrya --manifest-directory <manifest-directory> # Directory where manifests are located [default: .]
comtrya --manifests <manifests> # Run a subset of your manifests, comma separated list
A manifest is a collection of packages and files, and this will likely be expanded upon later. A Manifest is a logcal grouping of resources that can be "appied" to your machine, and fetched from remote locations or local.
Packages & Files
Currently, Comtrya can install packages and provision files. Pretty simple at the moment.
- ensure: installed
Install several packages with the list version:
- ensure: installed
- from: gitconfig
You should take a look at the issues page (on GitLab, not GitHub) to see what's available to contribute. Below is a short list of the major features that are upcoming.
println!'s pretty much everything. We need to use a proper logging library to restrict the scope of the output and should provide a summary output.
Comtrya finished in 12.3s
Installed Packages: 12
Provisioned Files: 34
We're using petgraph to build out the graph, but we're not travesing it in a way that will allow us to concurrently execute manifests at the same depth. This is something I wish to sort out pretty soon.
TODO: Allow manifest directory and variables to be configured in a
Package Provider Enhancements
Currently, we execute arbitrary
packager install commands. The provider spec should be enriched to support:
- Already installed lookups
- List refresh
- Version pinning
- Packager installation
- If Homebrew doesn't exist, offer to install it
- If Nix doesn't exist, offer to install it
Currently, files were prototyped pretty quickly. There's the ability to render and create files on a disk; we need to provide context providers to enrich the templating.
Also, symlinking only works if there's no rendering to take place; but there's no flag to encourage / enforce this.