HTTP(S) proxy
We strongly recommend including a production-grade HTTP(S) proxy in each deployment of Elimity Insights. For our SaaS customers we include this by default. Theoretically you could let the Elimity Insights server handle HTTP(S) requests directly, but using a proxy gives you dedicated support for various configuration options:
related to TLS: certificates, cipher suites, protocol versions, ...
related to HTTP: HTTP-to-HTTPS redirects, health checks, request body size limits, timeouts, ...
Most cloud providers offer an HTTP(S) proxy (e.g. Google Cloud Load Balancing, Azure Load Balancer) that integrates well with their CaaS / VMaaS products. If using your cloud provider's proxy is not an option, then installing one manually on e.g. Windows Server is also possible. We suggest to take a look at Caddy, a widely-used open-source HTTPS server with excellent proxying capabilities. The remainder of this page contains some additional guidelines for setting up Caddy as an HTTP(S) proxy for Elimity Insights on Windows Server.
Installing Caddy on Windows Server
To install Caddy as an HTTP(S) proxy for Elimity Insights on Windows Server we recommend to just deploy their official Docker image. Refer to the snippet below as a starting point for your docker-compose.yml file:
services:
caddy:
image: caddy
ports:
- 80:80
- 443:443
restart: always
volumes:
- .\caddy:C:\etc\caddy
insights:
image: europe-west1-docker.pkg.dev/elimity-general/docker/insights:v3.41.0-nanoserver-ltsc2022
restart: always
volumes:
- .\insights:C:\app\config Of course you'll also need to configure Caddy. The official documentation includes a great tutorial about writing Caddyfiles, here's a template you can build on (place it at .\caddy\Caddyfile):
Last updated