modd VS goingo

There's also modd[0] which allows for many file watch pattern -> command combos to easily be defined & run simultaneously from a modd.conf file.

[0]https://github.com/cortesi/modd

i was using cortesi/modd for this while using docker. Since I change to Rancher with dockerd i wasn’t able to get live reloading working again, i also tried air but no luck.. out of curiosity did anyone have a similar issue?

Interesting. I've been using https://github.com/cortesi/modd for this for a while but I'll check this project out.

me likes: https://github.com/cortesi/modd A little more flexible for various files

I use a somewhat similar approach for Pirsch [0]. It's build so that I can run it locally, basically as a fully fledged staging environment. Databases run in Docker, everything else is started using modd [1]. This has proven to be a good setup for quick iterations and testing. I can quickly run all tests on my laptop (Go and TypeScript) and even import data from production to see if the statistics are correct for real data. Of course, there are some things that need to be mocked, like automated backups, but so fare it turns out to work really well.

You can find more on our blog [2] if you would like to know more.

[0] https://pirsch.io

[1] https://github.com/cortesi/modd

[2] https://pirsch.io/blog/techstack/

This pair of tools do both front-end and back-end live reloading with a small amount of config: https://github.com/cortesi/modd https://github.com/cortesi/devd

Go makes pretty bad WebAssembly. It only embeds in Javascript, and it's at least 2MB for Hello World. You can't really use it in server-side engines like wasmer/wasmtime.

TinyGo is far better, but only supports a subset of Go's stdlib.

I'm playing with TinyGo, and using GPRC communication with the outer engine as a poor substitute for WASM interface types.

https://github.com/fizx/goingo if you want to read the ugly prototype!