donothing
do-nothing scripting framework (by danslimmon)
runnable-plans
A half-measure between "this recurring task is documented on a page somewhere" and "this recurring task is automated" (by vatine)
| donothing | runnable-plans | |
|---|---|---|
| 1 | 1 | |
| 80 | 4 | |
| - | - | |
| 0.0 | 0.0 | |
| almost 3 years ago | about 1 year ago | |
| Go | Python | |
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
donothing
Posts with mentions or reviews of donothing.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-02.
-
Do-nothing scripting: the key to gradual automation
The author has written a Golang version of the same as well [1].
1: https://github.com/danslimmon/donothing
runnable-plans
Posts with mentions or reviews of runnable-plans.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-02.
-
Do-nothing scripting: the key to gradual automation
This is basically why I ended up writing Runnable Plans, over at https://github.com/vatine/runnable-plans/, the main differences are "you define the plan in YAML" (yeah, horrible, but better than hand-chasing a parser, that MAY come at a later date) instead of "in the script", "the plan has no inherent order" (to allow for future parallel execution), "saves success/failure to allow for later restart", and "can generate a GraphViz graph of the plan dependency ordering".
But, whatever works, works. Start somewhere, get it into a script, plan, whatever. Then, it is easier to identify steps that can be turned to entirely machine-operated.
What are some alternatives?
When comparing donothing and runnable-plans you can also consider the following projects:
Runbook - A framework for gradual system automation
Camunda BPM - Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
babushka - Test-driven sysadmin.