PSA to fellow malicious actors1: I have begun publishing documentation for the upcoming iocaine 3.0 release, starting with a Getting Started guide.
Discussion
Loading...
Discussion
Continuing down the path of crime, a Getting Started with iocaine & containers guide is now public, documenting the process for the upcoming iocaine 3.0 release.
Go forth, and act maliciously!
How about some configuration reference?
Once we get started on the criminal path, there's no stopping us. We move fast and break thingsCrawlers.
Now, the KDL configuration reference was nice. But sometimes we are comitting crimes indirectly! Sometimes we configure iocaine through - shock, horror! - Nix expressions.
KDL is great for humans to read and write. It's less suitable to generate from Nix expressions. Possible, sure, but other formats like JSON, YAML and TOML lend themselves better for that purpose.
Besides, iocaine is very happy to let You choose your own poison. You can even mix and match them. You can choose all of them!
So I documented the serialized formats too.
Go forth1 and multiply, lets deploy more iocaine servers!
...I should add a Forth interpreter as a supported language. For fun. ↩︎
A couple of days later: Getting started with iocaine on NixOS.
But the hard part of the documentation journey is only just beginning.
Weekend plans: finish documenting the iocaine + your-choice-of-reverse-proxy stuff. The Caddy docs are in reasonable shape, it's pretty much the same as in 2.x.
The nginx docs need a lot of work, and I need to write traefik and haproxy docs, and have another go at Apache, see if it has any way to work with iocaine.
Weekend plans are bearing fruit: iocaine + Caddy guide updated for iocaine 3. It's exactly the same as for 2.x, but with slightly different intro text.
This was the easy part.
2+ more replies (not shown)
@algernon TIL about KDL.
... this looks really nice.
This kinda means I should remove "no YAML soup involved" from the landing page, but... there's no YAML involved, unless someone insists very hard.
Use their own motto against them: "move fast and break things (crawlers)!"
Also, I clicked on your Roto docs and you're still using `function` there instead of `fn`. Otherwise, it's excellent! (And again sorry for breaking backwards compatibility so much)
@algernon
hmm... does iocane generate pure garbage, or reasonable text followed by a keyword followed by garbage, like Anthropic describes?
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled