No description
https://hoard.rs
|
|
||
|---|---|---|
| .github | ||
| book | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| cliff.toml | ||
| clippy.toml | ||
| config.toml.sample | ||
| CONTRIBUTING.md | ||
| deny.toml | ||
| Dockerfile | ||
| knope.toml | ||
| LICENSE | ||
| Makefile.toml | ||
| operation_upgrade_test.sh | ||
| README.md | ||
| renovate.json | ||
Hoard
hoard is a program for backing up files from across a filesystem into a single directory
and restoring them later.
Most people will know these programs as "dotfile managers," where dotfiles are configuration
files on *nix (read: non-Windows) systems. Files on *nix systems are marked as hidden by
starting the file name with a dot (.).
Documentation
You can find all documentation at https://hoard.rs.
Configuration
See config.toml.sample for a documented example configuration file.
Testing
Hoard's runtime behavior depends on environment variables, which the tests override to prevent polluting the developer's system and/or home directory. Because of this, tests must be run in one of two ways:
- Single-threaded, using
cargo make test-single-threadorcargo test -- --test-threads=1. - As separate processes with their own environments, using
cargo make test-nextestorcargo nextest run.
cargo-makeshould install the dependency automatically. Otherwise, runcargo install cargo-nextest.
Tests can also be run in a container using cargo make docker-tests.
License
