Documentation reports
Liberty Next → Document → Documentation reports writes the documentation of the installation as it stands — a deliverable for a project, a hand-over, an audit of the configuration — as a PDF or in Markdown. Superusers only.
At a glance
The two reports
| Report | For | Sections |
|---|---|---|
| Implementation report — technical and functional documentation of the install | The project team, the customer. | Context, Architecture, Applications and menus, Screens, Connectors and pools, Dashboards and Explorer, Operations, Security, Reference data; on demand, the appendices Settings — every setting, secrets masked — and API reference. |
| Technical report — developer documentation | The people who maintain the install. | Scope, Architecture, Data model, Configuration reference, API reference, Command line, Build and packaging, Appendix: code references. |
Producing one
- Open the report's card.
- Tick the sections — All / None —; the counter shows N of M sections. The technical report offers two options: detail every API route, and include the code snippets in the appendix — long.
- Under Settings, pick the Language — Français or English — and, if needed, the Date label of the cover page; by default, today.
- Download the PDF, or Markdown to edit it further.
Every value whose name says it is a secret — passwords, keys, tokens — is masked, and so are the connection addresses.
Related
- Developer reference — the same knowledge, browsable.