hailin 7fb0168dc5 fix: keep voice-service on bridge networking to avoid port conflict ... iconsulting-llm-gateway already occupies port 3008 on the host. voice-service only has a single TCP port (no docker-proxy overhead), so bridge networking with 13008:3008 mapping is sufficient. Only livekit-server and voice-agent need host mode (UDP port ranges). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-01 20:23:13 -08:00
..
nginx	feat: add deployment scripts with SSL support for production	2026-02-09 17:44:27 -08:00
scripts	.	2026-02-19 20:37:19 +08:00
.env.example	Initial commit: IT0 AI-powered server cluster operations platform	2026-02-08 22:54:37 -08:00
deploy.sh	.	2026-02-19 20:37:19 +08:00
docker-compose.ssl.yml	fix: add Dockerfiles and fix docker-compose build configuration	2026-02-19 04:31:23 -08:00
docker-compose.voice.yml	fix: add Dockerfiles and fix docker-compose build configuration	2026-02-19 04:31:23 -08:00
docker-compose.yml	fix: keep voice-service on bridge networking to avoid port conflict	2026-03-01 20:23:13 -08:00
livekit.yaml	fix: expose TURN relay ports for NAT traversal	2026-02-28 11:39:50 -08:00