💾 Archived View for rawtext.club › ~sloum › geminilist › 002432.gmi captured on 2020-10-31 at 14:32:34. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Kevin Sangeelee kevin at susa.net
Mon Aug 17 00:05:54 BST 2020
- - - - - - - - - - - - - - - - - - -
Your nimble file requires a more recent build of Nim (1.3.x) than thelatest binaries release (1.2.6), yet it seems to build fine on 1.2.6.Was this just an oversight, or will I run into problems?
Interesting regardless, my first Nim compile - thanks!
Kevin
On Sun, 16 Aug 2020 at 23:26, <idf31 at memeware.net> wrote:
Hello. I've recently discovered Gemini, and I am really interested in
it! I have surfed the Gopherspace for some time, and I find Gemini very
neat as a modern Small Internet Protocol. I have decided to make a
server for the gemini protocol, more like an exercise. I want it to have
a small codebase and be light on resources(my apologies if this sounds
repetitive). I plan to use it in the future to host a bigger scale
project in the gemini-space, so the end-goal is still an usable and
secure server that could be used in real life. Any suggestion or help is
appreciated, as this is my first attempt at making a server.
The source code is located here: https://github.com/IDF31/geminim
To build it you would need the Nim programming language. You can install
it here: https://nim-lang.org/install.html.
Then to compile it you run "nimble -d:ssl build" in the source
directory. For now it expects a certificate "mycert.pem" and a private
key "mykey.pem" in the same directory as the binary for the TLS
connection, a configuration system will be added soon(tm).
The server is(for now) looking for a directory named "pub" in the same
directory as the binary.
It uses the default gemini port(1965).