Feature Request: Optional SSL/TLS support for HTTPS

[mjfork]

Description

Currently, the server only supports HTTP connections. For deployments that require secure connections (e.g., when exposing the server over a network, using with reverse proxies that expect HTTPS, or for compliance requirements), there's no built-in way to enable HTTPS.

Proposed Solution

Add optional SSL/TLS support via environment variables:

• SSL_CERT: Path to the SSL certificate file
• SSL_KEY: Path to the private key file

When both variables are configured and the files exist, the server automatically uses HTTPS. Otherwise, it falls back to HTTP (maintaining backward compatibility).

Example Configuration

# In .env file
SSL_CERT=/path/to/certificate.crt
SSL_KEY=/path/to/private.key
PORT=443

Use Cases

• Secure deployments accessible over networks (e.g., Tailscale, VPN)
• Compliance requirements that mandate encrypted connections
• Integration with tools that expect HTTPS endpoints
• Development environments that need to test HTTPS functionality

Implementation Notes

• Zero impact when SSL variables are not set (HTTP remains default)
• Graceful fallback if certificate files don't exist
• Works with self-signed certificates, Let's Encrypt, or any valid SSL cert

---

🤖 Generated with Claude Code