Crates.io | cargo-hatch |
lib.rs | cargo-hatch |
version | |
source | src |
created_at | 2021-09-11 13:35:25.544325 |
updated_at | 2024-12-08 12:09:41.184198 |
description | Hatch new projects like a chick coming out of its egg. |
homepage | https://github.com/dnaka91/cargo-hatch |
repository | https://github.com/dnaka91/cargo-hatch |
max_upload_size | |
id | 449715 |
Cargo.toml error: | TOML parse error at line 25, column 1 | 25 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Hatch new projects like a chick coming out of its egg.
Cargo hatch is a cargo init
/cargo new
on steroids, allowing complex templates thanks to the
Tera engine. Additional template values can be configured and requested from the user during
execution.
cargo-generate
instead?This project was born out of frustration with cargo-generate. Although a great project it didn't work for me personally as I got SEGFAULTs and Git errors whenever I tried to generate a new project with it.
The main differences are:
local
subcommand that simply takes any directory
and treats it as template making it easy to test templates or have local private templates, Git
or not.To build this project have rust
and cargo
available in the latest version. rustup
is the recommended way of installing and managing the Rust toolchain.
Then run the following command to install this project:
cargo install cargo-hatch
Make sure that your cargo binary path (usually $HOME/.cargo/bin
) is available from your $PATH
.
The usage of cargo-hatch
is rather detailed and therefore lives in a separate file. Check out
USAGE.md for further instructions.
This project is licensed under the AGPL-3.0 License (or https://www.gnu.org/licenses/agpl-3.0.html).