One important limitation: I'd rather not add a new DNS entry for the host and can't dedicate port 80/443 to the service as the host already offers http(s). It seems relays require websocket at the root, though?
I'd like to provide a public Nostr relay on ftp.halifax.rwth-aachen.de, which currently has 20 GBit/sec of network connectivity, in addition to lots of CPU and disk space.
I have a strong preference for self-contained implementations making use of some strongly typed language (Go, Rust, Java, ...), and I'd be happy to provide some PostgreSQL backend. Could you recommend a mature implementation that is fit for the purpose?
I'm aware of https://nostr.how/en/relay-implementations, but I'd prefer some guidelines and hear from your experiences.
Discussion
Is it possible to provide a nostr relay at wss://host/path, i.e. not at the root? nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6