29 lines
914 B
Markdown
29 lines
914 B
Markdown
# Qortal Node Reverse Proxy Templates
|
|
|
|
These templates are intended for installer automation. They expose a Qortal node as:
|
|
|
|
- API + `/render` via node API upstream (`12391`)
|
|
- QDN website/gateway fallback via node gateway upstream (`8080`)
|
|
- WebSockets via node API upstream
|
|
|
|
## Files
|
|
|
|
- `nginx-qortal-node.conf.template`
|
|
- `apache-qortal-node.conf.template`
|
|
|
|
## Placeholders
|
|
|
|
- `__QORTAL_PRIMARY_DOMAIN__` (Apache)
|
|
- `__QORTAL_SERVER_NAMES__` (Nginx)
|
|
- `__QORTAL_SERVER_ALIASES__` (Apache)
|
|
- `__TLS_CERT_PATH__`
|
|
- `__TLS_KEY_PATH__`
|
|
- `__QORTAL_API_UPSTREAM__` (example: `127.0.0.1:12391`)
|
|
- `__QORTAL_GATEWAY_UPSTREAM__` (example: `127.0.0.1:8080`)
|
|
|
|
## Notes
|
|
|
|
- Both templates include method/path hardening for sensitive endpoints.
|
|
- If using Let's Encrypt automation, render cert paths to your ACME-managed files.
|
|
- Keep `__QORTAL_API_UPSTREAM__` and `__QORTAL_GATEWAY_UPSTREAM__` internal-only when possible.
|