scripts-to-rule-them-all
cargo-make
scripts-to-rule-them-all | cargo-make | |
---|---|---|
8 | 26 | |
3,140 | 2,397 | |
- | - | |
0.0 | 9.2 | |
over 1 year ago | about 14 hours ago | |
Shell | Rust | |
Creative Commons Zero v1.0 Universal | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
scripts-to-rule-them-all
-
What’s with DevOps engineers using `make` of all things?
Personally I like https://github.blog/2015-06-30-scripts-to-rule-them-all/ as a pattern and then let the authors do whatever crazy thing they want from there. In my experience, 99% of repos never move past using simple shell scripts with a few common functions with that pattern, and things are kept fairly simple. A select few repositories tend to mature enough that they are able to invest in swapping towards something more testable than shell scripts, and then you just have a couple people who stick to invoking `make` from the scripts but it's fine and nobody has to think about it except them. We don't stick to that exact set of scripts, but find that as long as you don't use more than like 10ish entrypoints in `script/*`, and have at least `script/bootstrap` it's fine.
- Scripts to Rule Them All (2015)
-
Just: A Command Runner
I dig the general idea, but question the value add over a directory of `scripts` that follow sane conventions (ie `script/test`, `script/build` etc). Is the main thing that you can do `just -l` to see available commands? I have never really reached for `make` when I've had a choice, as I've done mostly ruby, JS, or java where you have more sane, humane tools (i.e. Rake, Yarn, Maven though that one is never fun).
My general approach is every repo should have something that follows https://github.com/github/scripts-to-rule-them-all, written in sh (maybe bash, its 2023), linted with shellcheck. When you need something fancy Rake is great or grab some nice bash command line helper and source it from all your scripts. Is a command listing really worth another dependency over what you get from `ls script` or `cat script/README` ?
- [AskJS] What is the best way to create a common npm package for building others?
-
Azure Pipeline running task in background?
Afaik AzDo cannot run tasks concurrently. From having had to work with azure pipelines I would highly suggest to use the github approach of Scripts to rule them all and avoiding predefined tasks unless absolutely necessary(Things that are complicated to implement and solutions already existing.
-
Why is uncoupled documentation bad?
GitHub have a pattern for this called "scripts to rule them all" - https://github.com/github/scripts-to-rule-them-all - I've not fully adopted it yet but I probably should, it looks very well thought-out.
-
Script up your projects
People at Github made an attempt to fix this situation: scripts to rule them all. The idea is to have common set of executable scripts for common developer tasks in a script/ directory in the root of every project:
-
How to Join a Team and Learn a Codebase
https://github.com/github/scripts-to-rule-them-all
cargo-make
-
Rust Tooling: 8 tools that will increase your productivity
cargo-make aims to be an extensive Rust-written task runner that additionally lets you define workflows to execute your tasks. You can install it using cargo install cargo-make.
- Cargo make: Rust task runner and build tool
-
Hey Rustaceans! Got a question? Ask here (49/2023)!
You might be interested in cargo-make, which is based on TOML, or Just, which has a syntax that is vaguely inspired by Make but much less weird sigils and more suited to non-file-based tasks.
-
Makefile equivalent in Rust ecosystem
I would like to rewrite this project in Rust, but I am not so familiar with Cargo as I am with Make. Is it possible to declare these kinds of rules and targets ? Should I use a build script, a custom tool like cargo-make or something else ? What do you think ?
-
Including a cargo command as a dev dependency
I use just myself, and I personally don't want projects' codebase to decide when something gets cargo installed on my system. For people who feel that's more acceptable, I'll note that cargo-make has first class support for the idea of expressing a task that depends on a cargo plugin:
-
Pain points using Rust for game dev ?
Thank you for the help, created ticket #787 and #788!
-
Just: A Command Runner
https://github.com/sagiegurari/cargo-make
I ended up using it over just because it felt easier to use cross platform, and toml seemed like a right choice
- Run python scripts before compilation using Cargo?
-
Created a simple tool for task automation in Rust
cargo make is used pretty extensively in Bottlerocket OS
-
Anyone use Rust to build SaaS web apps professionally?
Cargo is a pretty robust build tool on it's own, but for that extra automated workflow oomph, I also use cargo-make
What are some alternatives?
govuk_design_system_formbuild
just - 🤖 Just a command runner
django-sql-dashboard - Django app for building dashboards using raw SQL queries
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
govuk-form-builder - A form builder for Ruby on Rails that’s compatible with the GOV.UK Design System.
cargo-benchcmp - A small utility to compare Rust micro-benchmarks.
generate-package - Use as a sub-generator or plugin in your generator to create a package.json for a project. Or install globally and run with Generate's CLI.
rst - The open source design documentation tool for everybody [Moved to: https://github.com/vitiral/artifact]
pure-sh-bible - 📖 A collection of pure POSIX sh alternatives to external processes.
cargo-ebuild - cargo extension that can generate ebuilds using the in-tree eclasses
confgen - Generate repetitive configs for vite, typescript, eslint, etc
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml