2024-04-29 - [53] 2:10
I changed up Git, Gopher, and Finger support on my site to heavily simplify my personal use code base. These changes are:
This is for 2 reasons. The first reason is because I would prefer not to use nginx anymore (I might make a replacement for my needs or I may just decide that I'm fine without a proxy). The second reason is because I'd prefer to not have to rely on the git-http-backend cgi script. At the moment, I don't understand fastcgi or its parameters or cgi in general. As such, I'd prefer not to use it.
This means the way to fetch/clone/pull/etc my git repositories is to use git://vigrey.com instead of https://vigrey.com as the source.
There are going to be some negative consequences to this change. I understand that these issues will happen and apologize for them happening. Some of these consequences will be:
Even though those consequences will happen, I have made peace with the fact that those consequences will happen.
I feel a bit bad about this in particular. I'm a Minnesotan and want to generally support the Gopher protocol because it was made in Minnesota. With that said, removing support for it in Bergelmir will simplify Bergelmir quite a bit. It will also simplify a few other programs a bit to be able to remove gopher support on them. I was only serving static content from the gopher server. Getting rid of the server will save quite a bit of storage space.
My site is first and foremost a gemini capsule. Writing gemtext files has been much nicer for me than writing html. I'm fine with being able to serve over HTTP as well, cosidering the web is what people know.
The simplicity of the finger protocol interested me quite a bit. It was also nice to have a "miniblog" system instead of needing to write a full-sized blog post or microblog post on a platform like Mastodon or Twitter. I will still keep my finger log archive up.
Removing finger support will help simplify Bergelmir.
I quite like the idea of my site not loading any other resources for any page requested. My base site might end up adopting that concept, but no promises one way or the other. Due to how I want the http server to only load static content, I need to generate a lot of html files for the text.vigrey.com and vigrey.com versions of my site. I'd prefer to lower my storage requirements by not having to generate the text.vigrey.com content.
If you would like to reply to this post, feel free to send me an email or misfin message.
=> Email: vi@vigrey.com | Misfin: vi@vigrey.com This content has been proxied by September (ba2dc).Proxy Information
text/gemini; charset=UTF-8