Update setup
parent
4d35c46ae7
commit
46ec7ebea9
6
setup.md
6
setup.md
@ -7,7 +7,7 @@ These defaults are often not enough for each of the services to run, so you'll n
|
||||
|
||||
Supervisor is starting the various services inside the container, and below is the path to the configuration file expected.
|
||||
|
||||
## Mounts Required for Services
|
||||
## Mounts Required for Services and Default Ports
|
||||
| Service | Path | Port |
|
||||
| ------ | ------ | ---- |
|
||||
| binkd | /etc/binkd | 24554 |
|
||||
@ -22,7 +22,9 @@ This mounts are normally provided by the `-v` start command when starting a cont
|
||||
|
||||
The ports used by the services can be overridden by the `-p` for the host side or container side (and if you change the container side, you'll need to update the configuration file for the respective service).
|
||||
|
||||
NGINX is also used in the container, and it will forward anything coming from 24553 (TLS) to 24554 (non-TLS).
|
||||
NGINX is also used in the container, and it will forward anything coming from 24553 (TLS) to 24554 (non-TLS). You can modify that configuration by overwritting `binkps.conf` with a `-v` argument pointing to your own binkps.conf.
|
||||
|
||||
EG: `-v ${SRC}/binkps.conf:/etc/nginx/modules-enabled/binkps.conf`
|
||||
|
||||
## Additional Mounts
|
||||
| Service | Path |
|
||||
|
Reference in New Issue
Block a user