To edit the configuration, you need to understand how the YAML format works. It's pretty simple, and we have a brief guide below:
/var/lib/wisp/daemon/config/wisp.yaml
⚠ Apply your changes with wisp restart
<aside>
ℹ️ Some changes require you to edit the docker configuration in /var/lib/wisp/docker-compose.yml
</aside>
If you'd like to help us test daemon-specific features before they roll out to production, you can move to the beta
branch on a specific node.
/var/lib/wisp/docker-compose.yml
services:
bootstrapper:
environment:
- ENVIRONMENT=beta
Example of setting the daemon to BETA branch
Like any changes to the config files, you will need to reboot the daemon with wisp restart
for them to take effect. You can revert the change and use production releases again by changing it back to production
You can change the default port of the daemon and SFTP in the Admin Panel → Service Management → Nodes → Settings → Configuration tab. This will automatically update the daemon's (wisp.yaml
) configuration to the new ports, but you'll need to manually update the docker-compose.yml
and possibly wisp.yaml
if the automated update to it fails. Like any changes to the config files, you will need to reboot the daemon for them to take effect using wisp restart
/var/lib/wisp/daemon/config/wisp.yaml
web:
listen: ...
sftp:
port: ...
/var/lib/wisp/docker-compose.yml
services:
bootstrapper:
ports:
- '8080:8080'
- '2022:2022'
By default, the daemon binds to all IPs. If you want the WISP daemon to only bind to a single IP then you will need to make the following changes.
/var/lib/wisp/docker-compose.yml
services:
bootstrapper:
ports:
- '123.123.123.123:8080:8080'
- '123.123.123.123:2022:2022'
You can modify the interval at which server disk usage is checked.
/var/lib/wisp/daemon/config/wisp.yaml
internals:
disk_use_seconds: 30
Server file permissions are checked every time the server starts. This can take several minutes on servers with very large number of files.
/var/lib/wisp/daemon/config/wisp.yaml