SSL about server HOT 1 CLOSED

I actually thought that this was really common, but after searching for a while [1] [2] [3] [4] [5] [6] this pattern of loading the SSL through Node.js doesn't seem to be popular at all. The main reason is that the instance is behind a place and you can add the SSL straight there, as this has many added benefits.

So this is not abandoned, I just think it doesn't make sense to rush it through the 1.0.0 so it's being pushed down quite hard on the priority list.

If you really want to use server and you really want to support SSL in this way through Node.js, see about replacing the listen method of the express plugin for a custom one. This is officially not supported at all, won't be following SEMVER and you are responsible to set up ctx.server so websockets and others work properly later on.

[1] Cloudflare: through the proxy (I normally use this) https://revs.runtime-revolution.com/easy-ssl-with-heroku-cloudflare-62fc8535d6d4
[2] Heroku: through their platform https://devcenter.heroku.com/articles/ssl-endpoint
[3] Digital Ocean 1: Apache https://www.digitalocean.com/community/tutorials/how-to-create-a-ssl-certificate-on-apache-for-centos-6
[4] Digital Ocean 2: Nginx https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-14-04
[5] AWS: https://aws.amazon.com/certificate-manager/
[6] AWS 2: https://stackoverflow.com/a/44122928/938236

from server.