$ show deadc0de6/dotdrop
dotdrop is a command-line tool for managing dotfiles across multiple hosts using profiles, Jinja2 templating, actions, and transformations. It stores dotfiles in a Git repository and deploys them to target systems, allowing different configurations per host or environment. The architecture is modular: separate Python modules handle each operation (install, compare, update, import, remove, uninstall), with a central dispatcher in `dotdrop.py`. Configuration is defined in YAML (or optionally TOML) files that specify dotfiles, profiles, variables, actions, and transformations. Key entry points are the CLI subcommands invoked via `dotdrop <command>`. Data flows involve parsing the config, aggregating imported configs and variables, then executing file operations (copy, symlink, diff) with optional template rendering and shell commands. External dependencies include Jinja2, docopt, PyYAML, and optional libraries for TOML support and system detection. The codebase is well-tested with both Python unit tests and a large suite of Bash integration tests, and it is distributed via PyPI, Homebrew, AUR, Snap, and other channels.
The LLM identified 4 files worth highlighting for reuse:
Abstract base class `DictParser` that converts YAML/TOML dictionaries into Python objects with automatic key adjustment (e.g., `link_by_default` to `link_by_default`). Provides a reusable pattern for parsing structured configuration into typed objects, decoupling parsing logic from business logic. Can be extracted and adapted for any project needing schema-based config parsing.
`Templategen` class wraps Jinja2 with custom delimiters (`{{@@ ... @@}}`), MIME-based file type detection, and dynamic loading of custom functions and filters from external files. It provides methods `generate` and `generate_string` for rendering templates. This component is self-contained and can be reused in any Python project requiring a configurable Jinja2 environment with file-type awareness.
`LinkTypes` enum defines five link modes (NOLINK, LINK, ABSOLUTE, RELATIVE, LINK_CHILDREN) with a `get()` class method for lookup by string. Demonstrates a clean, type-safe pattern for representing a fixed set of options with validation. Easily extractable for any project needing a similar enum-based configuration option.
`Logger` class provides structured logging methods (`log`, `sub`, `emph`, `err`, `warn`, `dbg`, `dry`, `ask`) with automatic color disabling on non-TTY output. It supports dry-run mode and interactive prompts. This is a reusable logging utility that can be dropped into any CLI application to provide consistent, color-coded output with minimal dependencies.