lrt VS modd

To do this well (for servers, which is the most common case) you need to keep the port open (and delay requests while recompilation is in progress) or clients can see transient errors. So it's probably not a language level concern, but a protocol level one (it's very solvable for HTTP for example).

I built https://github.com/superhuman/lrt which tries to solve this problem in a go-like way (no configuration required, minimal log noise, and reliability/simplicity as the primary design goals) for Superhuman.

Modd is a library that makes hot reloading possible in Go applications. To use it, install it on your machine using the command below:

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/