💾 Archived View for tilde.pink › ~slondr › geminex.gmi captured on 2024-02-05 at 10:11:59. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
a gemini server from the proton to the supercluster
I'm implementing a Gemini server that's trivial to start using with reasonable defaults, scales to however big you want it to, and allows for high levels of customization.
The goal of Geminex isn't to be "the Nginx of Gemini" or "the http.server of Gemini". The goal of Geminex is to be both of those at once. In other words, serving up your current working directory on port 1965 is as easy as
$ geminex start
On the other hand, advanced configuration is possible using command-line options or a TOML file. Setting geminex up as a system daemon is braindead easy (it's built into the release system!). Deploying geminex to multiple physical servers with internal load balancing is possible. (Getting all of those nodes to agree to serve files from the same directory is currently not easy.) Turing-complete configuration methods are planned.
It's capable of serving most simple requests and supporting a small amount of user configuration. I'm able to make requests to it using real clients and get proper responses, most of the time. However, many features remain unimplemented. Unless you're interested in helping out with development, you probably don't want to use it just yet.
Development happens on Sourcehut.
Eventually, when geminex is ready for prime-time usage, I'll likely migrate this landing page to a self-hosted box somewhere.