Joachim Van Herwegen 4223dcf8a4 feat: Split up server creation and request handling
This allows us to decouple the WebSocket listening from the HTTP configs,
making these features completely orthogonal.
2022-11-09 09:10:00 +01:00
..
2022-05-05 11:20:53 +02:00

HTTP

Options related to the base support of HTTP requests by the server.

Handler

Sets up all the handlers a request will potentially pass through.

  • default: The full setup, that is middleware + static files + IDP + LDP.
  • simple: A simpler setup in which the IDP is disabled.

Middleware

A set of handlers that will always be run on all requests to add some metadata and then pass the request along.

  • no-websockets: The default setup but without the websocket-related metadata.
  • websockets: The default setup with several handlers.

Server-Factory

The factory used to create the actual server object.

  • no-websockets: Only HTTP.
  • websockets: HTTP and websockets.
  • https-no-websockets: Only HTTPS. Adds 2 new CLI params to set the key/cert paths.
  • https-websockets: HTTPS and websockets. Adds 2 new CLI params to set the key/cert paths.
  • https-example: An example configuration to use HTTPS directly at the server (instead of at a reverse proxy) by adding the key/cert paths to the config itself.

Static

Support for static files that should be found at a specific path.

  • default: The default handler with a favicon and css for the IDP. New entries can easily be added for new files.