[ANN] Git front-end for Gemini

[Frederick Yin]

On 6/14/20 2:11 PM, lel wrote:
> It looks like the page at gemini://fkfd.me/git/cgi sends a bad header line. 

Just FYI, jetforce doesn't inform git.gmi of the existence of a slash at
the end of a CGI PATH_INFO, so `/git/cgi` and `/git/cgi/` are requests
for the same page; but the relative links differ in behavior: `=> tree/`
links to `/git/tree/` and `/git/cgi/tree/`, respectively.

> The server responds with a header of `20 SUCCESS text/gemini`, which means a status code of 20 (which means success), and a mime type of "SUCCESS text/gemini", which isn't a valid mime type, and isn't recognized as one by any client I know of. Looking in gemini://fkfd.me/git/const.py, it seems you define all of your status codes this way. Just replying with `20' is the behavior required for a client to know what to do with your response.

Oh! I totally let slip of that. My testing client doesn't care about
mimetypes; it just renders in text/gemini whatsoever. It should be
correct in the next commit.

> Having changed that, I haven't been able to get anything other than 42 statuses on your demo or a server of my own, but I'm sure there's some way to fix it, like you mention in your announcement. This could still be beyond way cool tho, given that gemini requires the web to proliferate itself rn, outside of just hosting tarballs or whatever.

I haven't written up the Usage part yet in the documentation. You need
to change a few hardwired lines like the shebang in the CGI entry
executable, `cgi`, as well as other configs in `const.py`. I'll get
around to it.

~fkfd