Network Settings
Self-Hosted
Bind to different port or interface
SysReptor is bound to port 8000 on localhost by default. If you want to bind it to a different port, use the BIND_PORT
environment variable and restart your containers from the deploy
directory.
The format is IP:HOST_PORT:CONTAINER_PORT
(note that CONTAINER_PORT
should always be 8000).
Examples: | |
---|---|
1 2 3 4 |
|
Export port variable and run container | |
---|---|
1 2 3 |
|
Export port variable and run container | |
---|---|
1 2 3 |
|
Binding SysReptor to a publicly reachable network port exposes the application to untrusted networks without encryption. We recommend setting up a web server.
Make sure that environment variables are set persistently, e.g. by adding the export
command to your ~/.profile
.
Proxy Configuration
We pass the proxy environment variables (HTTP_PROXY
and HTTPS_PROXY
) from your host system into the Docker containers. To use a proxy, set those variables on your host system and start your containers from the deploy
directory.
Export proxy variables and run container | |
---|---|
1 2 3 4 |
|
Export proxy variables and run container | |
---|---|
1 2 3 4 |
|
The proxy server must be reachable from container
Make sure that the proxy server is reachable from inside your docker container.
Loopback addresses (e. g. 127.0.0.1
) or localhost
will not work.
Make sure that environment variables are set persistently, e.g. by adding the export
command to your ~/.profile
.
CA Certificates
Your proxy server will probably not have a publicly trusted CA certificate. Build your Docker image with custom CA certificates:
Set CA certificate, build and run | |
---|---|
1 2 3 |
|
Set CA certificate, build and run | |
---|---|
1 2 3 |
|
Make sure that environment variables are set persistently, e.g. by adding the export
command to your ~/.profile
.