How to humanely publish a project with HTTPS certificates #4944
Replies: 2 comments
-
Hi, thanks for your feedback. In most production setups, handling HTTPS is typically delegated to a reverse proxy such as Nginx, Traefik, Caddy, or Apache. These tools are designed specifically to manage TLS certificates, handle protocol negotiation, and provide better security and performance for public-facing endpoints. Managing HTTPS directly within the application is generally discouraged, as it introduces complexity and security risks that are better handled by dedicated, battle-tested software. |
Beta Was this translation helpful? Give feedback.
-
I found this solution for myself. Maybe it will be useful to someone.. #/bin/server.ts const APP_ROOT = new URL('../', import.meta.url); const sslOptions = { new Ignitor(APP_ROOT, { importer: IMPORTER }) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why is there no normal instructions anywhere on how to publish a project with certificates without HTTPS crutches? The absence of this functionality makes the framework non grata. Using a second web server for these purposes is pornography. Manually editing something that should work out of the box is terrible. Please provide a way to simply specify the path to the certificates and the protocol type in ENV - so that it works, like a human being. Thanks in advance. I'll go try to find a way to launch my project with HTTPS..
Beta Was this translation helpful? Give feedback.
All reactions