Enabling HTTPS access

HTTPS access can be enabled only for docker-compose deployments.

1. Create a certs directory under config/ssl-proxy. For a Linux or Unix-based OS, use:

mkdir config/ssl-proxy/certs

2. Place your certificate and key under the newly created directory:

config/ssl-proxy/certs
├── mydomain.key
└── mydomain.pem

3. Set your domain name and file names for your key and certificates in config/ssl-proxy/conf.d-ssl/nginx.conf under the server directive:

...
server {
	...
	ssl_certificate /etc/nginx/certs/<your_certificate_filename>;
	ssl_certificate_key /etc/nginx/certs/<your_key_filename>;
	...
}
...

With the file names from step 2, the configuration looks like:

server {
	...
	ssl_certificate /etc/nginx/certs/mydomain.pem;  # set your certificate filename here 
	ssl_certificate_key /etc/nginx/certs/mydomain.key; # set your key filename here 
	...
}
...

4. Enable ssl-proxy by editing your custom.env configuration and adding the ssl-proxy mod:

COMPOSE_FILE=docker-compose.yml:mods/ssl-proxy.yml

5. Run make up in the project's root to update your docker-compose deployment.

You can now access the Databand UI by using the ssl-proxy container and HTTPS.