Tootfinder

Opt-in global Mastodon full text search. Join the index!

@cdp1337@social.bitsnbytes.dev
2026-03-29 13:25:15
    WarlockBackend\Lib\VendorName\VendorNameApi:
arguments:
$VendorNameApiKey: '%VendorName.api_key%'

WarlockBackend\Lib\VendorName\VendorNameMods:
arguments:
$VendorNameApiKey: '%VendorName.api_key%'

Yup, having to have yaml registrations for each and every damned library is gonna get real old, real quick...

@frankel@mastodon.top
2026-04-25 09:12:03

How to Write Your First #OpenTelemetry Declarative Config File with Trace
oneuptime.com/blog/post/2026-0

@portaloffreedom@social.linux.pizza
2026-02-23 22:15:02

- yaml is a terribile file format.
- norway, what are you talking about? It's great!

@datascience@genomic.social
2026-03-23 11:00:00

GitHub Actions for the R language: Makes automatic testing of your R package much easier and making sure your package works on different OS and R versions is a matter of just a few lines of yaml: #rstats

@cdamian@rls.social
2026-04-10 08:37:06

Friday Links 26-12
Two weeks of links. A lot of AI related articles again. I liked the paper about using chatbots in leadership, and the one about the YAML of the mind.
If you want a podcast, check out the one about night trains.
christof.damian.net/2026/04/fr

@jamesthebard@social.linux.pizza
2026-03-11 17:31:22

Documentation continues. Done with the `queue` and `worker` endpoints, probably about 50% of the way done with this. I still need a good way to package all of this up with the binary which means putting the `openapi.yaml` file somewhere on the net so it can be pulled if need be. I'll deal with that later...lol
#openapi

OpenAPI being rendered by Scalar as nice documentation.  Shows the 5 queue routes and 5 worker routes along with model information.
A ton of YAML that comprises the OpenAPI file.  Still have a ton of work left to do.
@alexanderadam@ruby.social
2026-03-10 00:40:21

You're looking for something that's readable but more efficient and smaller than #JSON or #YAML?
Structure data with #ASCII control codes like people did in 1963!

@crell@phpc.social
2026-04-15 16:54:27

The future...

A post from Johann Sathianathen, @johann_sath

It reads:

saas is dead

openclaw replaced all my
subscriptions

went from $480/month on tools
to $1,245/month on API costs & 15
hours a week fixing yaml files

adapt or be left behind
@michabbb@social.vivaldi.net
2026-02-18 17:39:24

⚡ Distinguishes real outages from regional blips using multi-site consensus data
📦 MIT licensed - install via #RubyGems, configure probes in YAML or Ruby classes
github.com/basecamp/upright

@ripienaar@devco.social
2026-04-10 08:17:06

I really dont understand the infatuation people have with this 'task' command, the UX is so so poor.
$ task -l
* build-bundles: Build testing bundles
$ cat taskfile.yaml | yq '.tasks|keys'
- b
- fast-bench
- bench
- bench-graph
....28 more
Ridiculous

@mgorny@social.treehouse.systems
2026-02-05 20:09:03

"#GitHub Actions Is Slowly Killing Your Engineering Team"
#Azure over GitHub. Yes, they managed to make something worse. Much worse.

@jamesthebard@social.linux.pizza
2026-03-11 18:35:11

Almost 600 lines of OpenAPI documentation later and I'm done. I think I'll package the `/doc` endpoint with the Docker images since I can just copy over the static directory and have it live in the container. I'll add directions on how to add the docs to the standalone binaries as well which should cover that use case. Overall, it turned out pretty well.
#sisyphus

VSCodium showing the tail-end of the OpenAPI YAML file with the final line number being 592.
The final Scalar API docs string for Sisyphus showing all of the implemented routes.
@michabbb@social.vivaldi.net
2026-04-11 20:08:15

/perf-check /seo-audit /a11y-audit /compliance-check
🔄 Persistent session state in YAML Markdown:
📌 Phase tracking & file manifests
📌 Token usage per agent
📌 Error logs & retry counts
📌 Reliable resume after interruptions
🏗️ Guided design dialogue with depth-selectable reasoning (Quick/Standard/Deep), built-in codebase investigation, and 2-3 architectural approaches with trade-offs before any code is written

@jamesthebard@social.linux.pizza
2026-03-11 05:04:19

Now the pain in the ass part: documenting all of the routes. I think I'm gonna use Scalar because it's easy and I'm pretty lazy. Carved off the `/doc` directory to host the `openapi.yaml` and `index.html` files. So far, got one single endpoint documented...lol
#openapi #sisyphus

The `/doc` page showing the Sisyphus Server API documentation for v2.0.1.
Actually executing the GET request on the `/queue` endpoint.  The page shows the response and a ton of options that I'm kinda digging.
@mgorny@social.treehouse.systems
2026-03-30 17:03:09

Totally normal workflow:
I work on documenting #Jinja syntax used in #CondaForge recipes.
#Prism doesn't have one. But Internets suggest Twig would work instead.
#Docusaurus. But there's a workaround.
github.com/facebook/docusaurus
So I copy the code over to the project, fix it and while at it, rename it to "jinja" and adjust a bit.
But then, highlighting Jinja expressions alone looks pretty bleak, so let's combine it with YAML… Hmm, that actually doesn't work that well, needs some more adjustments. And before you know it, I have a pretty new Jinja highlighter, and a recipe highlighter that combines Jinja expressions, YAML, v0 recipe selectors, v1 if:/skip: conditions, and also highlighting shell / cmd variables for a good measure.
github.com/conda-forge/conda-f