libconfini
cue
libconfini | cue | |
---|---|---|
8 | 112 | |
155 | 4,835 | |
- | 1.7% | |
0.0 | 9.9 | |
almost 2 years ago | 4 days ago | |
C | Go | |
GNU General Public License v3.0 only | 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.
libconfini
-
Why the fuck are we templating YAML? (2019)
Personally I prefer INI over nearly all configuration formats.
https://github.com/madmurphy/libconfini/wiki/An-INI-critique...
- An INI Critique of TOML
- Do you call it an "ini" file or a "dot I N I" file?
- libconfini: Yet another INI parser
- An INI critique of TOML
-
YAML: The Missing Battery in Python
Essentially the reasons given here. (This is from an INI parser developer, but I don’t think it’s particularly biased.)
- If a linux/unix was rewritten today, what would be different?
cue
-
Show HN: Brioche – A new Nix-like package manager
Agreed on all counts, especially the central issue with nix and the properties that I'd want out of a replacement. I think CUE ( https://cuelang.org/ ) is a perfect language for this.
-
Ask HN: Anyone dislike GitHub action yml syntax
I write my GHA in CUE now, though I am moving to Argo more generally (which I also write in CUE)
https://cuelang.org | https://cuetorials.com
-
Really: Policy language for infra that doesn't suck
While not implemented, here is the CUE creator's writeup about how CUE can be a better alternative to rego. The main advantage is that the policies can be written separately and then unified. I don't see how I might have more modular or composable policy building blocks with Really.
https://github.com/cue-lang/cue/discussions/818
-
TypeSpec: A New Language for API-Centric Development
If you are in a situation where you have a backend and you want to expose an API and then you would eventually want a client, you would need format specs as the starting point where server and clients are generated from that one source.
At the moment, OpenAPI with YAML is the only way to go but you can't easily split the spec into separate files as you would do any program with packages, modules and what not.
There are third party tools[0] which are archived and the libraries they depend upon are up for adoption.
In that space, either you can use something like cue language 1] or something like TypeSpec which is purpose built for this so yet, this seems like a great tool although I have not tried it yet myself.
[0]. https://github.com/APIDevTools/swagger-cli
[1]. https://cuelang.org/
EDIT: formating
-
Show HN: Workout Tracker – self-hosted, single binary web application
Where `kube.cue` sets reasonable defaults (e.g. image is /). The "cluster" runs on a mini PC in my basement, and I have a small Digital Ocean VM with a static IP acting as an ingress (networking via Tailscale). Backups to cloud storage with restic, alerting/monitoring with Prometheus/Grafana, Caddy/Tailscale for local ingress.
[1] https://www.talos.dev/
[2] https://cuelang.org/
-
Apple releases Pkl – onfiguration as code language
I've been somewhat surprised that CUE bills itself as "tooling friendly" and doesn't yet have a language server- the number one bit of tooling most devs use for a particular language.
I'm assuming it's becaus CUE is still unstable?
Anyway, if others are interested in CUE's LSP work, I think https://github.com/cue-lang/cue/issues/142 is the issue to subscribe to
-
Why the fuck are we templating YAML? (2019)
This is where I usually pitch in with "Have your heard of CUELang, our lord and savior?": https://cuelang.org/
- Not turing complete
-
10 Ways for Kubernetes Declarative Configuration Management
CUE: The core problem CUE solves is "type checking", which is mainly used in configuration constraint verification scenarios and simple cloud native configuration scenarios.
-
Lua is a viable alternative for JSON
If you really want executable configurations please consider a newer language like https://dascript.org or https://cuelang.org which provide better type safety.
1- https://news.ycombinator.com/item?id=38030778
-
Writerside – a new technical writing environment from JetBrains
Markdown and XML are nice, but what about more advanced documentation formats like OpenAPI? For one recent project, I set up automatic generation of the OpenAPI docs from (much more compact and flexible) CUE definitions (https://cuelang.org/) - which has the bonus of also being able to test the API against the definitions. JetBrains has a CUE plugin, but it's really barebones (doesn't even support jumping from the usage of a schema to its definition). Of course the possibilities when generating docs are endless (just think of the various syntaxes for doc comments, embedding examples/tests in source code etc.)...
What are some alternatives?
config-parser - A slim, fully managed C# library for reading/writing .ini, .conf, .cfg etc configuration files.
dhall-lang - Maintainable configuration files
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
jsonnet - Jsonnet - The data templating language
ini-parser - Read/Write an INI file the easy way!
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
toml - Tom's Obvious, Minimal Language
starlark-rust - A Rust implementation of the Starlark language
crudini - A utility for manipulating ini files
Protobuf - Protocol Buffers - Google's data interchange format
guile-gi - Bindings for GObject Introspection and libgirepository for Guile
jsonnet-libs - Grafana Labs' Jsonnet libraries