Configuration¶
Environment variables¶
| Variable | Description | Default |
|---|---|---|
WEB_HOST |
Web server bind address (0.0.0.0 for Docker/production) |
localhost |
WEB_PORT |
Web server port | 8082 |
BLUESKY_SERVER_HOST |
BlueSky server hostname/IP address | localhost |
FLASK_ENV |
Set to production for production deployment |
— |
Binding for containers
WEB_HOST defaults to localhost for security. Production and Docker
deployments must set WEB_HOST=0.0.0.0 so the server is reachable from
outside the container.
Additional variables for the integrated build:
| Variable | Description | Default |
|---|---|---|
WEBATM_INTEGRATED |
Set to 1 to enable the integrated backend hooks |
unset |
WEBATM_AUTO_START |
Set to 0 to disable first-boot BlueSky auto-start |
enabled |
WEBATM_AUTOSTART_MARKER |
Path of the first-boot marker file | /dev/shm/webatm_autostart.done |
Network ports¶
| Port | Direction | Purpose |
|---|---|---|
8082 |
browser → WebATM | Web interface (HTTP + Socket.IO) |
11000 |
WebATM → BlueSky | Command port — sending simulation commands and events |
11001 |
BlueSky → WebATM | Data port — receiving real-time simulation data |
Important
The BlueSky ports (11000/11001) are not configurable. Ensure your BlueSky server runs with the default port configuration.
Production deployment checklist¶
- Configure environment variables in
docker-compose.yml. - Set
FLASK_ENV=productionandWEB_HOST=0.0.0.0. - Deploy with
docker-compose up -d. - Monitor with
docker-compose psanddocker-compose logs -f webatm.
Security features¶
- Capability dropping and no-new-privileges in Docker.
- Session tracking with Socket.IO ping/pong connection monitoring.
- Environment-based configuration.