Configuration Basics
KiloCenter configuration files and baseline settings — config.docker.yaml, KC-Core, KC-Gateway, port mappings.
Goal
Understand and verify baseline runtime configuration for a local deployment.
Configuration Files
kilocenter-modules/config/config.docker.yaml-- KC-Core configuration (container mode)kilocenter-modules/KC-Core/config.yaml-- KC-Core configuration (source dev mode)kilocenter-modules/KC-Gateway/config.yaml-- KC-Gateway configuration (source dev mode)kilocenter-modules/docker-compose.yml-- service definitions and port mappings
Container Mode Defaults
In container mode, KC-Core reads config/config.docker.yaml. All service addresses use Docker service DNS names (e.g., postgres, redis, mosquitto). Environment variables in .env override the compose defaults.
Source Dev Mode Defaults
kilocenter-modules/start-dev.sh exports environment variables and auto-detects the PostgreSQL port:
If Docker container
kilocenter-postgresis running, it uses port5433.Otherwise, it falls back to
5432for a host-local PostgreSQL.
Settings to Verify Before Testing
Database: host, port, credentials (default:
localhost:5433, userkilocenter, passwordchangeme)KC-Core health: port
8086KC-Gateway gRPC-web: port
9090KC-Gateway health: port
8087BSSCI: port
5000, TLS certificate pathsSCACI: port
5001, TLS certificate pathsMQTT: broker host, port, and credentials
TLS Certificate Paths
BSSCI and SCACI TLS certificate paths are configured under the protocol section in KC-Core/config.yaml (source dev) or config/config.docker.yaml (container):
Paths in the source dev config are relative to the KC-Core working directory. Container config uses absolute paths (/app/certificates/). Generate certificates before first start — see Docker Compose Installation.
Default Credentials
These defaults exist for local development convenience. Change them for any non-local deployment:
PostgreSQL: user
kilocenter, passwordchangemeMQTT broker: user
admin, passwordKiloCenterAVA base station factory login:
ubuntu/123456
MQTT Integration
MQTT is disabled by default in KC-Core/config.yaml:
To enable MQTT, set enabled: true and restart KC-Core. The Mosquitto broker must be running (it is included in the Docker Compose stack). See MQTT First Steps for integration details.
Validation Checklist
KC-Core starts without errors and
/healthresponds on port8086KC-Gateway starts and
/healthresponds on port8087Container mode: KC-Web loads at
http://localhost/Source dev mode: KC-Web loads at
http://localhost:5173KC-Web can reach KC-Gateway on port
9090(gRPC-web requests succeed in browser console)
Last updated