Oli

Yes, this probably is Docker related. It depends on how you invoke a command within a Dockerfile. Seems like Umbrel added a workaround for this: https://github.com/getumbrel/docker-nostr-rs-relay/blob/master/Dockerfile#L27 (`ENTRYPOINT` is handled differently...

Can you provide some logs of a failed recovery attempt on 0.18.x? I don't think there's something wrong with recovery in general (that would've shown up in at least one...

Thanks for the additional info. I'll look into it a bit more then.

Can you rebase the PR to get rid of the merge commits please? Then I'll take another look.

Thanks for the rebase. Looks a bit better now. Unfortunately there's another bit of learning ahead of you. Open Source is quite demanding in terms of git proficiency, since crafting...

Are you sure you installed go 1.22 correctly? If you run `go version` do you get 1.22.4? Older versions (I think before 1.20) will not understand the new 3-part go...

Okay, I see. Your `go 1.22.4` installation/binary is accessible as `go1.22.4` instead of just `go`. That's why the make command doesn't work, since it uses the old version. The installation...

> Not only it seems not up-to-date (mentions 1.19) but also breaks user-wide compatibility of previous go binary with whatever other projects might be requiring go binary, possibly affects other...

I can compile the current `master` branch just fine with `go 1.21.0`, so the `.4` in the `go.mod` is not the issue. It's that `make` explicitly uses the `go` binary...

Of course you'd need to specify the `GOCC` parameter when using `make` that way, that's the whole point of the PR. But it seems to be working. The warnings are...