Advanced Configuration

This chapter outlines ways to achieve custom and advanced setups.

Custom service configuration

In the previous steps you used the .env configuration files created in the Docker Compose directories config/aura-web, config/aura-playout and config/aura-recorder. In most common setup scenarios all configuration done with environment variables is sufficient.

For some more advanced setups or debug purposes, there are also sample configuration files for each service under /opt/aura/config/services/sample-config available. To overwrite any service configuration, simply copy its configuration file to the parent services folder.

Only use these overrides if you are an advanced user, or are advised to do so.

Nginx and Reverse Proxy

In the AURA Web setup all services are made reachable behind a reverse Proxy. This Nginx-based setup also supports SSL via Let’s Encrypt.

Behind second Reverse Proxy on different Hosts

If you have another reverse proxy in your Organization, which terminates TLS and does the routing for all your other services, Aura-Web does support this by disabling Certbot (Let’s Encrypt) and communicate via http. To do this you can just use port 80 of this Host. We assume what your hosts are communicating in your internal network, because all that communication is unencrypted http traffic.

Basic Config on 1st Reverse Proxy

  • The 1st Reverse Proxy must listen on Port 443 (https) and needs to route your incoming aura-web traffic to your Aura-Web host to Port 80

  • Your 1st RP needs to terminate TLS

  • At the Moment we cannot support URL rewrites

Config Aura-Web on 2nd Host

  • Aura-Web needs to listen on Port 80

  • Disable Certbot

      AURA_HOST_CERTBOT_ENABLE=false

  • Keep # AURA_HOST_PROTO=http commented out!

    • Our internal components need to know that they are being served via https, for their redirects and external API endpoints to work.

1st and 2nd Reverse Proxy on same Host

At the moment running another reverse proxy on the same machine isn’t officially supported with this setup, since there’s no possibility to close ports with an override. Be aware that the Docker Compose by default opens ports 80 and 443. To keep this running you may need to adjust the ngnix config and docker-compose.yml

Disable Nginx

If you wish to not use Nginx whatsoever, you can override the Docker Compose with the following content:

services:
  nginx:
    deploy:
      replicas: 0

This disables the internal Nginx. Keep in mind the nginx does a lot of heavy lifting to handle all redirections and URL rewrites correctly, which you will then need to handle manually.

If you wish to expand the nginx-config you can put further configs into the custom-folder. Keep in mind the configs need to end on .conf.