Server/Configuration: Difference between revisions
From Bondix Wiki
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
By default, the server configuration in <code>/etc/bondixserver.json</code> allows to set up many things via the web interface - environments and tunnels that are created dynamically (via the web interface) are stored in /etc/bondix/. | By default, the server configuration in <code>/etc/bondixserver.json</code> allows to set up many things via the web interface - environments and tunnels that are created dynamically (via the web interface) are stored in /etc/bondix/. | ||
However, you can customize | However, you can customize Bondix server to adjust your requirements, such as: | ||
* Have the web interface only accessible on a dedicated IP/port | * Have the web interface only accessible on a dedicated IP/port | ||
Latest revision as of 12:20, 9 December 2025
Server Configuration
By default, the server configuration in /etc/bondixserver.json allows to set up many things via the web interface - environments and tunnels that are created dynamically (via the web interface) are stored in /etc/bondix/.
However, you can customize Bondix server to adjust your requirements, such as:
- Have the web interface only accessible on a dedicated IP/port
- Disable the webinterface completely
- Set up tunnels statically
Configuration Layout for /etc/bondixserver.json
Configuration is stored in JSON, as an array of configuration commands. Lets inspect the default configuration:
[
{"target": "tunnel", "action": "set-settings-location", "directory": "/etc/bondix/"},
{"target": "server", "action": "add-https", "host": "0.0.0.0", "port": "443", "allowMonitor": true},
{"target": "server", "action": "add-http", "host": "0.0.0.0", "port": "80", "allowMonitor": true},
{"target": "server", "action": "add-user", "user": "admin", "password": "password"},
{"target": "server", "action": "set-web-login", "password": "password"}
]