Agate - A simple gemini server

[timconsidine]

@DidierMalenfant a thought, just a thought, you know more about this

I saw Kineto : https://git.sr.ht/~sircmpwn/kineto
If I understand it correctly, it proxies gemini:// to http://
It's only 3 .go files (plus licence and readme)

If it were built into your agate deployment, would that deliver an app which effectively serves both gemini and http ?
That would be boost to some wanting to use gemini but not have their site only accessible in Lagrange etc.
Avoids an external proxy dependency like Smolnet

I think Cloudron base image supports go.

Tell me to shut up if I am barking up the wrong tree
<woof> <woof>

[DidierMalenfant]

@timconsidine said in Agate - A simple gemini server:

If it were built into your agate deployment, would that deliver an app which effectively serves both gemini and http ?

It looks like it could work. What I'm not sure is:

• How do we make it an option so that people who don't want http can have it off.
• It doesn't seem to return when launched so how do we run both this and agate side by side?
• How safe is the http server for this? The one I use for the health check, Caddy, is pretty well supported and widely used. I don't know about this one.

[timconsidine]

@DidierMalenfant good points.
I just thought that as something was being served on http, it might as well be a version of the capsule.
It’s your package so don’t let me push it in a wrong direction.

[DidierMalenfant]

I think as an option it's a really good idea. I'll look into it if I get a chance.

[LoudLemur]

@DidierMalenfant if you are setting up some go files, how about goaccess for beautiful analytics, too?
https://goaccess.io/

[timconsidine]

I fail to see the point of analytics on anything except larger sites.
If you want to publish, publish and be damned, and who cares who sees it or not.
Rest is ego.

[LoudLemur]

@timconsidine Well, it is good fun to see from which country you have a visitor, and maybe if you make it to double or even triple figure readership. If you are less confident in your skills, it helps you feel that you have the site up and running, too!

[timconsidine]

The split world of http vs gemini protocol has been bugging me.
It's stupid and unacceptable.

So, inspired by @DidierMalenfant work on packaging Agate, I have also done a package, with the extra feature that it serves gemini .gmi files as both native gemini protocol, and as a basic http rendered view.

So it doesn't matter whether you use a regular browser or a gemini protocol browser, you still see the site.
No browser plugins needed, no need of external proxy site.

Need to do some testing of more gemtext features, images, links etc.
Then I will package it up on git.cloudron.io

Wasted a lot of time attempting to package twins which is supposed to serve Gemini and http, but I couldn't get it to work.
So I re-invented the wheel - stupid to do so, but at least it is working.

[timconsidine]

I did it :

https://forum.cloudron.io/topic/14082/agate-dual-protocol-gemini-http-browser

• dual protocol,
• single app,
• single domain,
• single content source,
• both worlds served

Temporary demo site : gem.appx.uk
no protocol specified because traditional browser will supply https:// and Gemini browser will supply gemini://

[DidierMalenfant]

Nice one!

[LoudLemur]

@timconsidine said in Agate - A simple gemini server:

gem.appx.uk

Elegantly done, @timconsidine !

I think there is a problem in the lovely demo page your provided. If you visit the links section in a gemini browser, the "Gemtext Summary" and "Cheatsheet summary" links don't work properly. Perhaps it is because Flounder is offline:
https://gemini.flounder.online/

[timconsidine]

@LoudLemur thanks for reporting
it seems the url is wrongly launched
I need to investigate
it has trailing characters
delete after .gmi, and their site is up
will look at the link

[timconsidine]

@LoudLemur about the broken link
I have fixed it in the sample file, and you can fix in <1. minute in your deployed application, if it's still running.

• go to File Manager
• open content folder
• open index.gmi
• scroll down to the links section
• remove the "$0" after the '.gmi' on the last 2 links

No idea how they got there, copy paste error by me probably.

Just to get you up and running with testing