# 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. For this Nginx is
used. Here we also offer support for using SSL via Let's Encrypt.

Be aware that the Docker Compose by default opens ports `80` and `443`. If you want to run
_AURA Web_ behind a reverse proxy on a different machine, you can just use port 80 of this
machine. At the moment running another reverse proxy on the same machine isn't supported with
this setup, since there's no possibility to close ports with an override.

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

```yaml
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`.