makesure
scripts-to-rule-them-all
makesure | scripts-to-rule-them-all | |
---|---|---|
13 | 8 | |
330 | 3,140 | |
- | - | |
9.2 | 0.0 | |
about 1 month ago | over 1 year ago | |
Shell | Shell | |
MIT License | Creative Commons Zero v1.0 Universal |
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.
makesure
- I stopped worrying and loved Makefiles
-
Show HN: Just.sh – compiler that turns Justfiles into portable shell scripts
makesure, a similar tool (https://maximullaris.com/makesure-vs-just.html) I'm developing, doesn't require installation in the traditional sense: https://github.com/xonixx/makesure#installation.
Also, I was considering adding the same feature (generating the equivalent shell script) to my tool, but after doing some analysis decided not to pursue this idea for the following reasons: https://github.com/xonixx/makesure/issues/83#issuecomment-98....
-
Just: A Command Runner
Another simple tool similar to this is makesure[1]. It’s written in shell so the idea is you include makesure itself in your repo, which avoids needing to install another tool to run commands on your project.
It’s very simple so isn’t good for everything, but works well as a simple command runner.
[1] https://github.com/xonixx/makesure
-
just VS makesure - a user suggested alternative
2 projects | 13 Aug 2022
-
run VS makesure - a user suggested alternative
2 projects | 13 Aug 2022
-
Frawk: A fast, JITted, statically-typed AWK written in Rust
- mawk (https://invisible-island.net/mawk/) - bundled in some Linux distros (?), known as the fastest byte-code compiled implementation.
All three have very good compatibility, but Gawk is super-set over POSIX standard. I have some evidence here, since I regularly test [1] against these implementations and even some others, like GoAWK.
[1] https://github.com/xonixx/makesure/actions/runs/1830978431
-
How did I run that code again? Tools to help recall
I've been using make to do this for ages, but its syntax really shows its age in a bad way. A while ago I switched to just (https://github.com/casey/just), which is a simple command runner with less unnecessary cruft (for my use case as a command runner) and a much saner syntax, and I've been pretty happy with it so far, I hardly ever need to look up anything.
There's also task (https://taskfile.dev/), which is YAML-based and might work well in an environment where everything else is YAML anyway, and makesure (https://github.com/xonixx/makesure), which is pretty similar to just, but didn't really click with me.
-
How to write idempotent Bash scripts · Fatih Arslan
yes, there is also https://github.com/xonixx/makesure - It is a simple task/command runner inspired by make with declarative goals and dependencies.
-
How to write idempotent Bash scripts
Idempotence is achievable elegantly with makesure tool [1] using @reached_if directive [2]. Full disclosure - I’m the author of the tool.
[1] https://github.com/xonixx/makesure
[2] https://github.com/xonixx/makesure#reached_if
- Show HN: Zero-install task/command runner implemented in Awk
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
What are some alternatives?
babashka - Native, fast starting Clojure interpreter for scripting
govuk_design_system_formbuild
rust_cmd_lib - Common rust command-line macros and utilities, to write shell-script like tasks in a clean, natural and rusty way
django-sql-dashboard - Django app for building dashboards using raw SQL queries
frawk - an efficient awk-like language
govuk-form-builder - A form builder for Ruby on Rails that’s compatible with the GOV.UK Design System.
scripts - Useful scripts that I find handy to work with
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.
run_lib - A bash script to help you organise and allow discovery of your project's scripts.
pure-sh-bible - 📖 A collection of pure POSIX sh alternatives to external processes.
PowerShell - PowerShell for every system!
confgen - Generate repetitive configs for vite, typescript, eslint, etc