sergetymo / kaksik Goto Github PK

Hi @sergetymo,

Your logger.ts example does not show any information about the client that sent the incoming request.

The IP address of the client is probably the most important information to log, so it would be nice if the Request class contained this information as well, in addition to the requested URL.

Congrats, kaksik seems to work just fine for self-hosted Gemini servers.

But I haven't had any luck deploying to Deno Deploy.

Here is what I get when deploying to Deno Deploy:

  deployctl deploy
  ℹ Using config file '.../deno.json'
  ✔ Deploying to project gemini-docs.
  ✔ Entrypoint: .../main.ts
  ℹ Uploading all files from the current dir (...)
  ✔ Found 14 assets.
  ✔ Uploaded 4 new assets.
  ✖ Deployment failed.
  error: The deployment failed: UNCAUGHT_EXCEPTION

  TypeError: Deno.listenTls is not a function
      at Application.start (https://deno.land/x/[email protected]/classes/Application.ts:32:24)
      at file:///src/main.ts:17:11

Here is main.ts:

import { Application } from './deps.mts';

const
isTest = Deno.env.get('THIS_IS_A_TEST'),
domain = isTest ? 'localhost' : '<my DNS address>',
app    = new Application({
  keyFile : `./cert/${domain}/key.pem`,
  certFile: `./cert/${domain}/cert.pem`,
})

app.use(ctx => {
  ctx.response.body = '# Hello World!'
})

await app.start()

Before deploying, I have uploaded my own RSA certificate and private key to the project, and Deno Deploy has accepted them. keyFile and certFile shouldn't be needed for Deno Deploy.

First of all, thanks for making such a nice Gemini server for Deno!

Have you considered adding support for Titan? I could give it a go, but I would need some tips or assistance to get started.

Hi @sergetymo,

While developing my JSdoc server capsule (gemini://qworum-jdoc.ddns.net/) using kaksik, I've found these 2 issues:

1. If the server has more than one parameterised route (i.e. one with /dir/:dirname and another one with /file/:filename), then only the first parameterised route is taken into account, the other parameterised routes are ignored.
2. Route parameters can't contain slashes (/), so they can't contain file paths.

I am filing these for future reference, I don't need an urgent fix for these personally.