💾 Archived View for bbs.geminispace.org › u › gemalaya › 5893 captured on 2024-05-10 at 12:27:48. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-03-21)
-=-=-=-=-=-=-
Re: "I've implemented a first version of a frontend gemini app..."
@flipperzero The misfin server (which uses the misfin protocol port 1958 by default) and the frontend (which uses the gemini protocol, port 1965 by default) can be configured to listen on different IPs. However, understandably, at the moment they need to be run on the same machine because the frontend needs to have access to the misfin identities (the frontend runs in a separate thread of the misfin server process). You can absolutely set it up as a subdomain, e.g gemmail.hashnix.club, the important thing is to correctly create the x509 cert with the right hostname for the gemini frontend. Hope that answered your questions.
2023-10-04 · 7 months ago
😺 gemalaya [OP] · 2023-10-05 at 16:34:
@flipperzero Latest version should make things easier. You can run the service as a daemon, and the frontend is served from the same socket (same port). Makes it easier to setup. "server-init" now requires the hostname/domain to be passed.
I've implemented a first version of a frontend gemini app for misfin (sort of like a webmail for misfin ^_^), i've pushed the changes in the devel branch. It works pretty well for me locally. What's supported right now: sign up (create a mailbox), reading the gembox, compose/send/reply. Try it with lagrange and use "Identity => Import" after sign up. As explained in the README.md, you need to create a certificate/key for the gemini app and copy them to service/frontend_cert.pem and service/...
💬 gemalaya · 12 comments · 2 likes · 2023-09-29 · 7 months ago