[REQUEST] Update Documentation about RELAY_PRIVATE_KEY

[pgerstbach]

Is your feature request related to a problem? Please describe.
It is unclear how to configure a paid relay so that it sends out the PNs with the invoice.

Describe the solution you'd like
Update documentation accordingly.

Describe alternatives you've considered
Without documentation I have tried the following. This might help to see what I was understanding based on the existing documentation:

• I set a secret in docker-compose.yml (and I can read it using docker exec <container-id> printenv SECRET)
• I assumed that a private key is generated automatically, because RELAY_PRIVATE_KEY default value is (auto-generated), however docker exec <container-id> printenv RELAY_PRIVATE_KEY returns nothing.
• Next assumption was that I might have to create a keypair myself, which seems to be the solution, but it is not obvious!

Thanks!

[jilv220]

Is it the SECRET variable now? I am also confused.

[pgerstbach]

It was explained by @cameri in Nostream-Telegram Group:
https://t.me/nostream_dev/4586

Ricardo Arturo, [16.02.2023, 14:38:32]:

• generate a private key with your favorite nostr client
• convert the nsec to hex securely (relays can't use nsec or npubs)
• then on your docker-compose.yml file, add a new environment variable called RELAY_PRIVATE_KEY and set it to the private key in hex