toast
cue
toast | cue | |
---|---|---|
10 | 109 | |
1,543 | 4,754 | |
- | 1.2% | |
7.6 | 9.7 | |
26 days ago | 7 days ago | |
Rust | Go | |
GNU General Public License v3.0 or later | 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.
toast
-
Taskfile: A Modern Alternative to Makefile
This looks a lot like Toast [1], except that Toast runs your tasks in a (more) reproducible containerized environment to help eliminate the "works on my machine" problem.
[1] https://github.com/stepchowfun/toast
- Non-Obvious Docker Uses
-
Ask HN: What developer tools would you like to see?
- A build system like Nix [1] but with a better user experience / more straightforward command-line tooling.
- A dependently typed programming language like Coq [2] (or Agda, Idris, Lean, etc.) that is sufficiently approachable to gain enough mindshare that companies start adopting it for mission-critical work.
- A version control system which scales to petabytes or more. Something that I could put large video files in without thinking twice about it. Something a large company could use for their monorepo—or even their data warehouse.
- A note-taking tool that allows me to organize notes in a graph with links between them (like a wiki), not as files and folders in a tree, which enforces the invariant that every note is transitively reachable from some "root" so I never lose a note.
- Something like Toast [3] but which is also designed for running services in production, not just local development and continuous integration. A unified way to run code in dev, test, and prod environments. A new k8s.
[1] https://nixos.org/
[2] https://coq.inria.fr/
[3] https://github.com/stepchowfun/toast (shameless plug)
-
One machine can go pretty far if you build things properly
I realize you are probably very busy, so feel free to say no...but could you glance at this Github listing and tell me if it is what I'm looking for...it seems correct, but I may be misunderstanding...
https://github.com/stepchowfun/toast
Thanks so much in advance...
- Toast: Containerize your development and CI environments
-
GitHub Actions by Example
If you're looking for an alternative way to reproduce your CI locally that isn't tied to a particular CI system (but which has a nice integration with GitHub Actions), there's also Toast: https://github.com/stepchowfun/toast
- Toast: A high-level containerized build system
-
Dockerizing a Programming Language
OP is using Docker + Make in a similar way to how I was a few years ago, before I started using Toast (https://github.com/stepchowfun/toast). Toast lets you define tasks like you would with Make (without all the hairy gotchas of Makefiles), but it runs them inside Docker containers for better portability/reproducibility.
-
Whats your favourite open source Rust project that needs more recognition?
toast: containerized workflow
cue
-
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.)...
-
Show HN: Config-file-validator – CLI tool to validate all your config files
It doesn't include validators for TOML and INI, but if you're doing JSON and YAML, I would take a look at using or building upon CUE (https://cuelang.org/). It is a different take on schema definition (plus more), and is surprising terse and powerful model.
- That's a Lot of YAML
- An INI Critique of TOML
What are some alternatives?
setup-msys2 - GitHub Action to setup MSYS2
dhall-lang - Maintainable configuration files
modus - A language for building Docker/OCI container images
jsonnet - Jsonnet - The data templating language
Plume - Federated blogging application, thanks to ActivityPub (now on https://git.joinplu.me/ — this is just a mirror)
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.
Iron - An Extensible, Concurrent Web Framework for Rust
starlark-rust - A Rust implementation of the Starlark language
gutenberg - A fast static site generator in a single binary with everything built-in. https://www.getzola.org
Protobuf - Protocol Buffers - Google's data interchange format
pest - The Elegant Parser
jsonnet-libs - Grafana Labs' Jsonnet libraries