💾 Archived View for rawtext.club › ~sloum › geminilist › 006347.gmi captured on 2024-02-05 at 11:00:50. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Robert "khuxkm" Miles khuxkm at tilde.team
Tue Apr 13 17:54:38 BST 2021
- - - - - - - - - - - - - - - - - - -
Just realized I forgot to link gemserv. My bad.
[1]: https://git.sr.ht/~int80h/gemserv
Just my two cents,Robert "khuxkm" Miles
April 13, 2021 12:52 PM, "Robert "khuxkm" Miles" <khuxkm at tilde.team> wrote:
April 13, 2021 10:50 AM, "Frank Jüdes" <Frank.Juedes at linux4specialists.com> wrote:
Hi Stephane,
Thank you very much for the update. That leaves me with three options now:
Actually there are four. :P
1. Try again to install Pythron 3.7+ on my stubborn development machine
(Oracle Lunix 7…)
2. Learn go really quickly and fork the Molly Brown server - i will
call it »the sunken Molly Brown server« in that case
3. Write my own gemini server from scratch in perl
4. Use literally any other Gemini server. gemserv[1], for instance, correctly implements PATH_INFO
(which is actually the issue here, since SCRIPT_PATH -
SCRIPT_NAME is as simple as figuring out
the base directory of the Gemini server) and SCRIPT_NAME (so you don't have to do the SCRIPT_PATH
trickery). There are others as well.
It really looks like only Molly Brown and JetForce have a usable CGI-implementation.
Again, gemserv and other servers have usable CGI implementations (including gemserv actually
implementing SCRIPT_NAME and PATH_INFO).
We should call it GGI, btw: Gemini Gateway Interface to distinguish it from CGI.
Why, exactly? I get the fact that you can't name your library CGI.pm, but that doesn't really
warrant changing the name of an entire technology. :P
Just my two cents,
Robert "khuxkm" Miles