Background
The current docs have solid reference material but no end-to-end guide showing how to put it all together for a real deployment. A single-server quickstart would serve as a concrete baseline — one OpenVox Server managing one or more agents — before the docs branch into more complex topics like scaling, compilers, and external CAs.
The Vox Pupuli docs have a relevant existing page at https://voxpupuli.org/docs/arch_single_server/ that covers similar ground and could serve as a reference or starting point (with author permission).
Scope
- Single OpenVox Server + agent
- Opinionated: pick the happy path, don't explain every option
- Stops before multi-server, compilers, external CA, or HA — those are separate topics
- Lives in the
openvox collection alongside the other quickstart docs, not in openvox-server
- Would give the existing tuning and scaling pages something concrete to anchor to ("starting from the single-server setup described here...")
Out of scope
- Multi-server / compiler setups
- Container/Kubernetes deployments
- External CA configuration
Questions for discussion
- Adapt the voxpupuli.org content (with author permission) or write fresh?
- Which OS(es) to target?
- Where exactly in the openvox nav — alongside existing quickstart entries?
Background
The current docs have solid reference material but no end-to-end guide showing how to put it all together for a real deployment. A single-server quickstart would serve as a concrete baseline — one OpenVox Server managing one or more agents — before the docs branch into more complex topics like scaling, compilers, and external CAs.
The Vox Pupuli docs have a relevant existing page at https://voxpupuli.org/docs/arch_single_server/ that covers similar ground and could serve as a reference or starting point (with author permission).
Scope
openvoxcollection alongside the other quickstart docs, not inopenvox-serverOut of scope
Questions for discussion