3 ms·
I'm not sure what existing off-the-shelf thing you would use instead. There is some overlap with things like docker-compose, serverless.yml, helm charts, etc.
by tyingq 4y ago
I'm not sure what existing off-the-shelf thing you would use instead. There is some overlap with things like docker-compose, serverless.yml, helm charts, etc. But each of those things is targeting a different use case and/or level of abstraction.
So if acorn is also a different use case or level of abstraction, it can't really reuse those formats. Their set of 8 top level structures[1] seems reasonable at first glance to me.
[1] args, profiles, containers, volumes, jobs, acorns, secrets, localData
- stingraycharles 4y agoI think the problem here is that it introduces a new syntax, not the configuration options itself. Why not just use yaml as a syntax? At the top of the document they already say it’s very similar anyway, I don’t see what this does that can’t be done with yaml? http://docs.acorn.io/authoring/overview http://docs.acorn.io/authoring/overview
- tyingq 4y agoAh yep. I didn't look carefully, and just assumed it was json, but looking again it's not.