lol lmdb. use one of the other storage drivers. the badger one is a tiny bit slower but guaranteed to build and not give you retarded errors like this.
that's why my relay #orlyπ¦ has one. 
if your system is linux, orly will just work for you, in fact you can just run the binary if your goal is just to run a relay for hosting or testing:
good that i saw this, i gotta fix the release workflow. latest will be on that. the binary you can see as i type this now v0.31.0 should be ok, there hasn't been any bugs reported since the ones that release fixed. new release includes some additions to the policy engine. put the libsecp256k1.so file next to the binary where you run it, as it looks there, or possibly you can put it elsewhere but that can be a pain.
also, if you have been looking at fiatjaf's code, you will notice that i do things quite differently, and the benchmarks, if you run them, will show you that it is faster than khatru and everything else.
plus, i answer questions and try to do my best and if i find any feature request you make interesting on its own account i might add it, though usually i would prefer to get paid some if you are gonna get paid for building the integration.
also, yes, i know its' web ui (also, it is the only relay with a web ui) is a bit clunky and buggy, but i'm not a front end dev, wouldn't have a clue much more than how to navigate svelte files to fix layout, i hate javascript. so if you have some javascript chops and want to fix it, please do, i will get around to improving it soon but i have a lot of other things i have to do.
Gitea
next.orly.dev
Total rewrite of ORLY to simplify and make it more robust
Gitea
next.orly.dev
Total rewrite of ORLY to simplify and make it more robust
