Replies (11)

bumi michael@getalby.com 2 years ago

why did the LNURL payment processor actually drop out of the readme?

1 replies ↓

Cameri🐦‍🔥 cameri@nostr.eco 2 years ago

I was never added

GitHub

feat: add LNURL processor (#202) · cameri/nostream@f237400

* feat: add new lnurl processor * fix: lnbits issues * fix: add default settings for lnurl processor * fix: small changes * fix: more changes ...

I just emailed Adithya to help me put the steps together to ensure we have them, but if you can help me I’d appreciate it! Btw I’ve added a whitelist for zap receipts for paid relays which is on by default.

2 replies ↓

Cameri🐦‍🔥 cameri@nostr.eco 2 years ago

it*

bumi michael@getalby.com 2 years ago

oh, I thought it was. sorry. I guess Adithya is best to help. I am a bit busy right now. but can check next week if it's not done by then.

1 replies ↓

Cameri🐦‍🔥 cameri@nostr.eco 2 years ago

no worries, thanks. I’ll try and ping you if that’s the case

Peter Gerstbach peter@gerstbach.at 2 years ago

Shouldn't there be a "env_file:" entry in docker-compose.yml? The default one does not have it, but the full guide in README.md assumes it is there.

1 replies ↓

Cameri🐦‍🔥 cameri@nostr.eco 2 years ago

turns out we don’t need that, rename your file to `.env` and remove the `env_file:` entry on your docker-compose.yml file

1 replies ↓

Peter Gerstbach peter@gerstbach.at 2 years ago

Well, this didn't work out for me, so I had to add the line backup docker-compose.yml. 🤔

1 replies ↓

Cameri🐦‍🔥 cameri@nostr.eco 2 years ago

oh i missed something. after adding the env vars to the `.env` file, on your docker-compose.yml you must add the env vars individually like: ENV_NAME: ${ENV_NAME}

1 replies ↓

Peter Gerstbach peter@gerstbach.at 2 years ago

I see, like it is done with "SECRET: ${SECRET}" right?

1 replies ↓

Cameri🐦‍🔥 cameri@nostr.eco 2 years ago

Yes sir