mastercontroller 1.3.0 → 1.3.2

package/docs/server-setup-https-credentials.md

@@ -1,32 +0,0 @@
-## Server setup: HTTPS with direct credentials
-
-Pass key/cert (and optional chain/ca) directly to `setupServer('https', credentials)`.
-
-### server.js (HTTPS credentials)
-```js
-const fs = require('fs');
-const master = require('./MasterControl');
-
-master.root = __dirname;
-master.environmentType = process.env.NODE_ENV || 'production';
-
-const credentials = {
-  key: fs.readFileSync('/etc/ssl/private/site.key'),
-  cert: fs.readFileSync('/etc/ssl/certs/site.crt'),
-  ca: fs.readFileSync('/etc/ssl/certs/chain.pem'),
-  minVersion: 'TLSv1.2',
-  honorCipherOrder: true,
-  ALPNProtocols: ['h2', 'http/1.1']
-};
-
-const server = master.setupServer('https', credentials);
-master.start(server);
-master.serverSettings({ httpPort: 8443, hostname: '0.0.0.0', requestTimeout: 60000 });
-master.startMVC('app');
-```
-
-### Notes
-- Use a high port (e.g., 8443) to avoid running as root, or grant `CAP_NET_BIND_SERVICE` if binding to 443.
-- Strong defaults are ensured if you omit them, but explicitly setting them is recommended.
-- For multiple domains, see the TLS/SNI guide.
-

package/docs/server-setup-https-env-tls-sni.md

@@ -1,62 +0,0 @@
-## Server setup: HTTPS via environment TLS (with SNI and live reload)
-
-This uses `config/environments/env.<env>.json` to configure TLS, SNI (multi-domain), HSTS, and watches cert files for live reload.
-
-### Example env.production.json
-```json
-{
-  "server": {
-    "httpPort": 8443,
-    "hostname": "0.0.0.0",
-    "requestTimeout": 60000,
-    "tls": {
-      "hsts": true,
-      "hstsMaxAge": 15552000,
-      "minVersion": "TLSv1.2",
-      "honorCipherOrder": true,
-      "alpnProtocols": ["h2", "http/1.1"],
-      "default": {
-        "keyPath": "/etc/ssl/private/site.key",
-        "certPath": "/etc/ssl/certs/site.crt",
-        "caPath": "/etc/ssl/certs/chain.pem"
-      },
-      "sni": {
-        "example.com": {
-          "keyPath": "/etc/ssl/private/example.key",
-          "certPath": "/etc/ssl/certs/example.crt",
-          "caPath": "/etc/ssl/certs/chain.pem"
-        },
-        "api.example.com": {
-          "keyPath": "/etc/ssl/private/api.key",
-          "certPath": "/etc/ssl/certs/api.crt",
-          "caPath": "/etc/ssl/certs/chain.pem"
-        }
-      }
-    }
-  }
-}
-```
-
-### server.js (HTTPS from env)
-```js
-const master = require('./MasterControl');
-
-master.root = __dirname;
-master.environmentType = process.env.NODE_ENV || 'production';
-
-// No credentials passed; MasterControl will auto-load TLS from env
-const server = master.setupServer('https');
-master.start(server);
-master.serverSettings(master.env.server);
-master.startMVC('app');
-
-// Optional: HTTP->HTTPS redirect (listen on 80)
-// master.startHttpToHttpsRedirect(80, '0.0.0.0');
-```
-
-### How it works
-- `default`: certs used when SNI domain does not match any entry.
-- `sni`: per-domain certificates; the server chooses the right cert via `SNICallback`.
-- Live reload: when any `keyPath`/`certPath`/`caPath` changes, the secure context is rebuilt in-memory (no restart needed).
-- HSTS: when enabled, responses over HTTPS include `strict-transport-security` with the configured max-age.
-

package/docs/server-setup-nginx-reverse-proxy.md

@@ -1,46 +0,0 @@
-## Server setup: Nginx reverse proxy with HTTP→HTTPS redirect
-
-Recommended production pattern: Node app on a high port (HTTP), Nginx on 80/443 handling TLS and redirects.
-
-### server.js (app on HTTP localhost:3000)
-```js
-const master = require('./MasterControl');
-
-master.root = __dirname;
-master.environmentType = process.env.NODE_ENV || 'production';
-
-const server = master.setupServer('http');
-master.start(server);
-master.serverSettings({ httpPort: 3000, hostname: '127.0.0.1', requestTimeout: 60000 });
-master.startMVC('app');
-```
-
-### Nginx config
-```nginx
-server {
-  listen 80;
-  server_name yourdomain.com;
-  return 301 https://$host$request_uri;
-}
-
-server {
-  listen 443 ssl http2;
-  server_name yourdomain.com;
-
-  ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
-  ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
-
-  location / {
-    proxy_pass http://127.0.0.1:3000;
-    proxy_set_header Host $host;
-    proxy_set_header X-Real-IP $remote_addr;
-    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-    proxy_set_header X-Forwarded-Proto $scheme;
-  }
-}
-```
-
-### Notes
-- Use certbot or another ACME client to manage certificates and renewals automatically.
-- This keeps Node unprivileged (no need to bind to 443) and simplifies TLS.
-