atmos VS ops-examples

This is why we created atmos to make it easier to manage large multi-account architectures. As a result, our components are reusable across organizations, regardless of how many accounts and regions they operate, and we minimize the snowflakes. And we avoid code generation, which is hard to thoroughly test in an automated fashion. Without naming names, lots of tools for terraform rely on code generation, but I see it as an anti-pattern that should be avoided.

sorry did not find anything advanced. A better tool to make terraform scaleable is https://atmos.tools

Workspaces are incredibly practical, and we leveraging them at-scale with literally thousands of workspaces using atmos for terraform. There is so much FUD around workspaces that is either ill-informed or based on outdated information. Any company using terraform at scale will rely on tooling and conventions. It's up to that tooling to ensure you are using terraform safely. Atmos is one of those tools. I'm not saying that you have to use workspaces, but just that there's nothing wrong with workspaces themselves.

Check out atmos for a fresh take at managing terraform configurations and terraform workflows. Instead of managing HCL `.tfvar` files manually for configuration, it uses YAML, and supports concepts of imports (via deep merging), remote imports (anything supported by gogetter), mixins, inheritance, multiple-inheritance, vendoring of root modules, workflows, task runners (via custom subcommands), and much more. There's a bit of a learning curve and mind-shift required if coming from a Terragrunt background, but the experience is mindblowing after switching to it. Also, it's not limited to terraform.

We obviously don't have a project for your exact use case, but we have an open-source example repo that shows a fairly advanced scenario of using the Terraform Spacelift Provider https://github.com/spacelift-io/demo-preview-environments-manager, a simple quickstart of using it https://github.com/spacelift-io/terraform-starter and you can also see the CloudPosse Atmos project, for a very advanced scenario which generates lot's of Stacks based on your component specifications https://github.com/cloudposse/atmos.

Yeh - we have a small language list here:

https://github.com/nanovms/ops-examples

If you're looking for a particular piece of software search on the repo first:

https://repo.ops.city/

If you don't find it and need help creating one ping me or open an issue in ops.

Nanos runs not just go but pretty much any language you want to throw at it:

https://github.com/nanovms/ops-examples .

FYI, erlang && elixir workloads can run on Nanos: https://github.com/nanovms/ops-examples/tree/master/elixir .

I do understand what you are asking for though. There used to be an older project called erlang-on-xen: https://github.com/cloudozer/ling .

It'd be great to see this idea revisited although you'll need to create some sort of new handling/framework.

See for example nanovm provides examples for a bunch of different languages, including this in Chicken Scheme https://github.com/nanovms/ops-examples/tree/master/scheme/01-hello-world ...I expect Racket would be possible too