Nostr Web Client

Keycast just got a heap of updates.

✨🔑✨ Highlights ✨🔑✨

🚢 Docker now actually builds properly 😮‍💨

🔌 Easier setup for your own domain. My recommendation is to use a separate caddy proxy container (there are instructions in the readme) to handle wiring up your own domain name to the app. This takes 2 minutes and manages all the SSL certs and reverse proxy settings for you.

⚙️ Easier config via a single .env file

⛔ New config for "allowed pubkeys" - make sure that only the people you want can use your instance of Keycast.

Find all the details here: 👇

https://github.com/erskingardner/keycast

fiatjaf 11mo ago

I just tried it and was able to create a team, add a key to it and generate a full-access bunker.

But then the bunker didn't do anything on https://jumble.social/ nor in https://metadata.nostr.com/, and when using it with nak event --sec '' I got a "Rejected" error.

What did I do wrong?

Reply to this note

Please Login to reply.

Discussion

JeffG 11mo ago

🙈 are you seeing any logs from the app? you can run `docker compose logs keycast-api` on your VM and you should get back the logs about what's going on.

JeffG 11mo ago

Ahh, nevermind. I know what the issue is 🤦‍♂️ Just forgot to start the signer process with docker. Fix incoming.

JeffG 11mo ago

nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcpzpmhxue69uhkummnw3ezumt0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5gapjsj should be all fixed now. I'd start over from scratch on your VM though. I've changed the way you initialize all the needed parts on your app. No more manually editing .env files, you just run an init bash script with some args. (Check the readme)

I've verified the signer is working on Jumble (and fixed a few bugs while In the process).

Thanks for keeping me honest! 🙏