scripts-to-rule-them-all
run
scripts-to-rule-them-all | run | |
---|---|---|
8 | 17 | |
3,140 | 474 | |
- | - | |
0.0 | 3.5 | |
over 1 year ago | 7 months ago | |
Shell | Go | |
Creative Commons Zero v1.0 Universal | MIT License |
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
run
-
Fig Has Joined AWS
I've been using Run [0] for this purposes.
[0]: https://github.com/TekWizely/run
-
Show HN: Xc – A Markdown Defined Task Runner
To the extent that posts like these evolve into discussing the merits of Make as a task runner, I would like to offer my tool for review:
* https://github.com/TekWizely/run
I built it to feel like make, but be better at managing tasks and wrappers.
If you are evaluating task runners and appreciate the simplicity of Make's syntax, I hope you'll give Run a try.
-
Just: A Command Runner
I invite you take a look at Run, a similar tool that I maintain:
* https://github.com/TekWizely/run
Support for including other Runfiles was recently introduced, with support for globbing and the ability to indicate if an error should be generated if no files are found.
- Automatic Makefile help generation
-
DevOps Is Bullshit
Unrelated to this topic, I invite you take a look at my project which a tool purpose-built to be a better version of what your makefile became:
Run: Task runner that helps you easily manage and invoke small scripts and wrappers
https://github.com/TekWizely/run
Defining commands feels like make, but comes with a bunch of extras targeted at the needs of a task-runner.
I hope you'll check it out!
-
sd – a cozy nest for your scripts
This looks like an interesting way to manage scripts globally. I could even see it able to manage n-sub-commands deep (vs usual "command sub-command" - maybe it already does?) by just trying to resolve each argument as a dir until you find a script to execute.
If you're interested in ways to better-manage small scripts and wrappers more locally, please take a look at my project, Run:
https://github.com/TekWizely/run
- Run v0.9.0 - Easily manage and invoke small scripts and wrappers - Now with support for Includes!
-
run VS makesure - a user suggested alternative
2 projects | 13 Aug 2022
-
The Unreasonable Effectiveness of Makefiles
For those looking for a powerful task runners that feel like a makefile, please take a look at Run:
https://github.com/TekWizely/run
It's better a managing and invoking tasks and generates help text from comments.
What are some alternatives?
govuk_design_system_formbuild
bashly - Bash command line framework and CLI generator
django-sql-dashboard - Django app for building dashboards using raw SQL queries
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
govuk-form-builder - A form builder for Ruby on Rails that’s compatible with the GOV.UK Design System.
pure-sh-bible - 📖 A collection of pure POSIX sh alternatives to external processes.
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.
doit - task management & automation tool
shtlang - A toy scripting dynamic imperative programming language.
confgen - Generate repetitive configs for vite, typescript, eslint, etc
Cake - :cake: Cake (C# Make) is a cross platform build automation system.