tjeh

Nginx TLS SNI routing, based on subdomain pattern

Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).
This works for http upstream servers, but also for other protocols, that can be secured with TLS.

prerequisites

• at least nginx 1.15.9 to use variables in ssl_certificate and ssl_certificate_key.
• check nginx -V for the following:

  ...
  TLS SNI support enabled

tjeh

{
  "name": "project-name",
  "description": "Template for static sites",
  "version": "1.0.0",
  "homepage": "http://www.project-name.com",
  "author": {
    "name": "Adam Reis",
    "url": "http://adam.reis.nz"
  },
  "license": "UNLICENSED",

tjeh

{
  "name": "Example",
  "version": "0.0.1",
  "description": "Example workflow",
  "author": "You <you@youremail.com>",
  "license": "MIT",
  "postcss": {
    "plugins": {
      "postcss-easy-import": {},
      "postcss-preset-env": {