tricorder
ocurrent
tricorder | ocurrent | |
---|---|---|
5 | 2 | |
50 | 135 | |
- | 0.7% | |
5.6 | 7.1 | |
7 months ago | 3 months ago | |
Rust | OCaml | |
MIT License | 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.
tricorder
-
Show HN: A new open-source automation tool as an alternative to Ansible/Salt
There is https://pyinfra.com/
As a sidenote, I also made a small experiment a while ago : https://github.com/linkdd/tricorder/
But it's a bit of a chicken-and-egg problem. Without users, I don't know how it should be used, without features I won't get any users. So for now, it's in a state of "I'll address bug reports and feature requests, but I won't actively develop it".
-
Ask HN: What's your favorite software testing framework and why?
Thank you. Your library seems nice.
Unfortunately, I have to say it... I hate YAML with a passion, k8s, github actions/gitlab ci, ansible, etc... When I'm doing ops jobs, I feel like I'm coding in YAML.
Btw, this hate for YAML birthed https://linkdd.github.io/tricorder/ :P
-
Created a simple tool for task automation in Rust
Another one in the same vein is tricorder, which has one of the coolest websites ever. AFAIK it doesn't do dependencies, though. But it's got a RUST API!
- Show HN: Automation the KISS way. No YAML involved
ocurrent
-
GitHub Actions could be so much better
Y axis is tool selection. Positive region of axis is “use a DSL”, lower region is “use a GeneralPurposeProgrammingLanguage”
The line starts at the origin, has a SMALL positive bump, than plummets downwards near vertically.
Gets it right? Tools like ocurrent (contrasted against GH actions) [1], cdk (contrasted against TF yaml) [2]
Gets it wrong? Well, see parent post. This made me so crazy at work (where seemingly everyone has been drinking the yaml dsl koolaide) that i built a local product simulator and yaml generator for their systems because “coding” against the product was so untenable.
[1] https://github.com/ocurrent/ocurrent/blob/master/doc/example...
-
Show HN: Automation the KISS way. No YAML involved
Keep working on this. It’s a splendid idea. Would be cool to eventually have a recipe where you import the crate, then program the deploy in rust, invoking your tool which builds my-build.rs, or a proper cargo build.
The following not true apples to apples, but pretty close. Rather than another crummy stringy DSL, the ocaml community said “we want to program our CI pipelines in OCaml”. So, they created https://github.com/ocurrent/ocurrent. You build your pipeline in an incredible language—then the CI server simply invokes your pipeline code, assuming you’ve implemented a basic interface.
What are some alternatives?
z-run - z-run -- scripting library lightweight Go-based tool
github-actions-typing - Bring type-safety to your GitHub actions' API!
testy - test helpers for more meaningful, readable, and fluent tests
LazySmallCheck2012 - Lazy SmallCheck with functional values and existentials!
act - Run your GitHub Actions locally 🚀
ospec - Noiseless testing framework
cheats - cheats allows you to create interactive cheat sheets for the command line.
php-easycheck - Mirror of http://chriswarbo.net/git/php-easycheck
automate - Native bash script for automate tasks in a multiple servers
azure-pipelines-agent - Azure Pipelines Agent 🚀