💾 Archived View for gemi.dev › gemini-mailing-list › 000261.gmi captured on 2024-08-19 at 00:00:48. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-12-28)

-=-=-=-=-=-=-

[ANN] Web based gemlog authoring

1. Brian Evans (b__m__e (a) mailfence.com)

I believe that avoiding the web entirely, with regard to gemini, is 
probably the best call. 
But that that leaves out a TON of people that lack the technical knowhow 
to ssh, rsync, git, etc.

As such, I have built a website that allows users to create accounts on my gemini server
and post content from simple web based forms. The site uses no js, no 
cookies, no session or
local storage, and no external stylesheet(s).

I am hopeful that as interest in gemini grows in non-developer communities 
the site may offer
a way for less technically inclined folks to add their voices to gemini space.

The site is specifically focused on "gemlogs"/journaling rather than on 
general content upload. 

The website and gemini URLs:

https://gemlog.blue
gemini://gemlog.blue

I'm still working through some things, but all of the basic functionality is working.

Small shout out to the creator of: https://proxy.vulpes.one
When a post is made, the content is linked via the proxy and has worked out quite well!

--?
Sent with https://mailfence.com
Secure and private email

Link to individual message.

2. Sean Conner (sean (a) conman.org)

It was thus said that the Great Brian Evans once stated:
> I believe that avoiding the web entirely, with regard to gemini, is 
probably the best call. 
> But that that leaves out a TON of people that lack the technical knowhow 
to ssh, rsync, git, etc.
> 
> As such, I have built a website that allows users to create accounts on 
my gemini server
> and post content from simple web based forms. The site uses no js, no 
cookies, no session or
> local storage, and no external stylesheet(s).
> 
> https://gemlog.blue
> gemini://gemlog.blue

  I saw on your Gemini post that you are trying to get editing and deleting
posts working.  A very silly, and out there suggestion---why not client
certificates?  Apache does support them, and there are HTTP methods that are
quite well suited to the task at hand (POST, PUT, DELETE).  You could set up
a method similar to Astrobotany to sign CSRs

	gemini://astrobotany.mozz.us/register

  Just an idea ...

  -spc

P.S. Here's the Apache config I created a few weeks ago when I started
looking into this:

<VirtualHost 192.168.1.10:443>
        ServerName      wiki.roswell.area51
        ServerAdmin     spc at conman.org
        DocumentRoot    /home/spc/web/wiki/htdocs
        ScriptAlias     /.cgi/ /home/spc/web/wiki/cgi-bin/
        AddHandler      cgi-script .cgi

        SSLEngine               on
        SSLCipherSuite          ALL
        SSLCACertificateFile    /home/spc/JAIL/etc/ssl/cert.pem
        SSLCertificateFile      /home/spc/web/wiki/cert.pem
        SSLCertificateKeyFile   /home/spc/web/wiki/key.pem
        SSLProtocol             +TLSv1.2

        <Directory /home/spc/web/wiki/cgi-bin>
                Options                 All
                AllowOverride           None
                Require                 valid-user
                Require                 ssl-verify-client
                SSLOptions              +StdEnvVars
                SSLVerifyClient         require
                SSLVerifyDepth          5
        </Directory>

        <Directory /home/spc/web/wiki/htdocs>
                Options         All -ExecCGI
                AllowOverride   None
                Require         all granted
                Script          PUT    /.cgi/put.cgi
                Script          DELETE /.cgi/delete.cgi
        </Directory>
</VirtualHost>

Link to individual message.

---

Previous Thread: [REQ] Element IDs in the web specification

Next Thread: SRV records