tao_at_garden

I've been looking for just a tool like this since Rewind was first introduced. Count me very interested!

I just ordered the tarot deck! Excited to see how it plays with Kult's published tarot adventure.

I've gotten a lot of value out of Dragons of Stormwreck Isle that came in the new D&D Starter Set. That said, I'm now using it as a base for jumping off into OSR (Old School Renaissance) modules after the OGL debacle and now this.

There's a number of solutions. One is to use a maintained Helm Library Chart that exposes all the values most could ever want like The Helmet [1]. The other is to move over to something like Timoni that is analogous to Helm but with better templating [2].

[1] https://github.com/companyinfo/helm-charts/tree/main/charts/...

[2] https://timoni.sh/comparison/

Podman as a devcontainers engine doesn't currently work rootlessly (the default) if you use devcontainer features [1] or (and this sounds like you're issue) if you use WSL2.

I haven't submitted the WSL2 issue to the Podman team yet. If you get to it before I do, can you link it here?

I've worked around the features bug by just using `devbox generate devcontainer` then adding all my desired container apps and services inside a `devbox.json` file.

[1] https://github.com/containers/podman/issues/18691#issuecomme...

Yes, there's us over at https://garden.io! We're big believers in pipelines that run anywhere. I even made a short little video that should give you the gist. [1]

Some of the short-list of differences: we use YAML for our configuration language, Dagger can use full-fat languages to define its pipelines. Our feature scope is broader: you can use us to vend IDP-like stacks to your developers if you're a Platform Team; we make development with remote Kubernetes clusters very easy, including all the remote image builds; and we have a number of integrations so you can bring your IaC tool of choice (Pulumi, Terraform) into your pipeline and set up service -> infra dependencies.

[1] https://www.youtube.com/watch?v=JFnan6s2cDg

And there's us, https://garden.io, that does totally portable CI pipelines with caching from builds to tests: https://github.com/garden-io/garden

I made an irreverent short on why your CI pipelines ought to be portable and runnable locally. Number one reason? Give your developers their time (and sanity) back. Pushing to Git in the inner loop disrupts flow and shatters attention.

https://www.youtube.com/watch?v=JFnan6s2cDg

I definitely don't have the budget for a Mk3 but I can see a number of original Launchpad Pros and Mk2s for sale on local websites for not much money. Count me in as another person interested!

The git commit, push, wait loop is terrible UX. Users deserve portable pipelines that run anywhere, including their local machines. I understand Act [1] goes some way to solving this headache but it's by and large not a true representation.

There are many pipelines you can't run locally, because they're production, for example, but there's no reason why we can't capture these workflows to run them locally at less-critical stages of development. Garden offers portable pipelines and then adds caching across your entire web of dependencies. Some of our customers see 80% or higher reductions in run times plus devs get that immediate feedback on what tests are failing or passing without pushing to git first using our Garden Workflows.

We're OSS. [2]

[1] https://github.com/nektos/act

[2] https://docs.garden.io

As a user of EXWM, I feel this deeply. That Wayland also requires just so much additional tooling to get things like screensharing working properly means that smaller distros, like Clear Linux, don't ship it.