Next Steps
Choose the next reading path for integration, configuration, deployment, or operations.
If readiness succeeds, both test UIDs connect, and messages flow in both directions, you have completed the local development loop.
Choose a path
Core Concepts
Learn channel ordering, message commits, users, devices, conversations, nodes, and Slots.
Integration
Divide product responsibilities and design authentication, messaging, and webhooks.
Tutorials
Continue with direct chat, group chat, and 100,000-member group paths.
Deployment
Start with topology and runtime medium, then complete configuration, verification, and production gates.
Choose an SDK
Choose by platform and access method, then follow its installation, capabilities, API, and upgrade path.
API & Protocols
Reference published APIs, the client-protocol core, and shared dictionaries.
Server Reference
Open configuration, operations, tooling, and architecture when needed.
Frequently asked questions
Is a single-node cluster a standalone mode?
No. It is a cluster with one node and still uses the Controller, Slot, Channel, routing, and persistence paths.
Can I use the example configuration in production?
No. At minimum, replace fixed credentials, plan TLS and access control, place data on managed durable storage, and validate capacity, failure recovery, and tail latency with the real workload.
Why does data remain after a restart?
The example stores node data in ./data/wukongim-single-node-data. Stopping the process does not delete that directory.
How do I change ports?
After copying wukongim.toml.example, edit the API, Manager, Gateway, and cluster listeners in the local wukongim.toml, then restart the node. Do not store machine-specific changes in the example template.
Why must production clients not call /user/token?
It is a demo identity endpoint. A trusted business backend must issue or update production tokens after real identity and authorization checks.
Where is the three-node environment?
The repository-root docker-compose.yml provides a three-node development environment. It exposes development credentials and benchmark capabilities, so it is not a production template either.
Documentation status
The bilingual paths listed here are published and enter search, sitemap, and LLM outputs. Discoverability means the content passed publication checks; it is not runtime acceptance for a target client, device, or production cluster.