nostr:nprofile1qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wa5x2ct59e5xzurs096xzan9wfhzucm09uqsuamnwvaz7tmwdaejumr0dshsdms043 is working on a relay monitor. What you store is up to you. I'd recommend checking my own implementation, grain 🌾. It's very configurable and has purging built in that you can fine tune with extensive whitelisting capabilities. Not much storage is needed unless you're running a mega relay and never purge. I have a couple dozen people whitelisted and it's using like 35mb. My relay also purges events from all non whitelisted users but allows anyone to write to it. When I implement WoT I'll also have a configuration for excluding WoT from purging. I had a lot of the same questions and no implementation was as configurable as Id like it to be without writing a bunch of external code, most likely in something I'm not proficient in. So I made my own implementation. GitHub is on my profile. There's also info about grain on my website linked in my profile. I'd be happy to help you set I up too if you'd like to try it.
Discussion
thanks bud, what are the hardware requirements for this ?
It takes very little resources from my testing. There are configurable resources limits. 😉
any link for the resources ? thanks
Oh I thought you meant computer resources. All you need to run grain is mongoDB server (community server linked in the readme) and grain itself. Check releases on GitHub for the latest binaries. There are binaries for both windows and Linux. Once mongo is running, all you need to do is run grain. It'll initialize the configs for you when you run it. Then you can change the configs to suit your use case.