| Crates.io | ruke |
| lib.rs | ruke |
| version | 0.1.10 |
| created_at | 2024-04-17 01:20:18.456947+00 |
| updated_at | 2024-05-18 23:12:57.74967+00 |
| description | A dead-simple automation tool. Inspired by Makefile and Justfile. |
| homepage | |
| repository | https://github.com/kauefraga/ruke |
| max_upload_size | |
| id | 1210906 |
| size | 44,699 |
A dead-simple automation tool. Inspired by Makefile and Justfile.
[!TIP] Looking for a Dockerfile/docker-compose.yml generator? gorvus is waiting for you!
Pre-requisites: Rust and Cargo.
cargo install ruke
First things first, you need to define your tasks in a Ruke.toml file.
Hopefully, Ruke can help you, just run
ruke init
With your Ruke.toml ready, now you need to run a specific task.
The syntax for running a task is ruke [target] where target is the task you wanna execute. Try this:
ruke
Obs.: the target task "main" is the default, therefore if you run ruke, it's the same as running ruke main.
ruke init - Create a Ruke.toml file with a task withinruke list - List existing tasksruke new - Create a new task (interactive mode)ruke add - Add a command to an existing task (interactive mode)ruke remove - Remove an existing task (interactive mode)ruke [target] - Run a specific taskruke init, ruke iruke list, ruke lsruke new, ruke nruke add, ruke aruke remove, ruke rm| Command | Flags |
|---|---|
ruke init |
doesn't have flags |
ruke list |
-m --minimal, -f --file <FILE> |
ruke new |
-n --name <NAME>, -f --file <FILE> |
ruke add |
-n --name <NAME>, -c --command <COMMAND>, -f --file <FILE> |
ruke remove |
-n --name <NAME>, -f --file <FILE> |
ruke [target] |
-q --quiet, -f --file <FILE> |
If you run ruke --help you'll see nice guide, and if you want help for a specific command, try ruke help [command].
ruke list --minimal will output less information (just tasks name) than ruke list.
ruke new -n "task-name" will create a new task named "task-name".
ruke add -n "task-name" -c "echo command-to-be-executed" will add the specified command in the task "task-name".
ruke remove -n "task-name" -f path/to/Ruke.toml will remove the task "task-name" from the Ruke.toml at an unexpected directory.
ruke build will run the task "build" and show you the outputs, while the ruke build -q will run silently.
I suggest you to use one of these two names: Ruke.toml or Rukefile, however, as long as you write a valid TOML, you can name the file whatever you want and pass it with the -f --file <FILE> flag.
Look at the full spec of TOML v1.0.0.
[tasks.main] # defines a task with an unique name
commands = ["go run cmd/main.go"] # defines a command array to be executed sequentially
[tasks.dev]
commands = ["pnpm dev"]
[tasks.build]
commands = ["go build -o gorvus cmd/main.go", "./gorvus"]
Feel free to contribute, create an issue to report a bug, suggest an API change, an improvement or a feature.
Thanks goes to these amazing people:
This project is licensed under the MIT License - See the LICENSE for more information.
Made with ❤ and 🦀 by Kauê Fraga Rodrigues.