Files
RustProxy/docs/README.md
T
2026-10-11 23:09:59 +02:00

5.0 KiB

RustProxy documentation index

This is the canonical index for the current project documentation. The authenticated administration documentation page at /docs embeds these Markdown files in its Reader tab and keeps OpenAPI/Swagger in a separate API tab.

Project and release

  • Project README - product overview, installation entry points and current release notes.
  • ROADMAP - planned and completed release scope.
  • CHANGELOG - user/operator-visible changes by release.
  • TODO - open work only; completed work is not retained as TODO.

Functional documentation

  • WEB_SERVER - reusable Web Services, static-file behavior, ranges/validators and document-root security.
  • PHP_FPM - implemented FastCGI/PHP-FPM integration, security model and runtime requirements.
  • PHP_FPM_ISOLATION - separate PHP-FPM pools to prevent cross-vhost INI settings leakage.
  • VHOSTS - vhosts and backend/source behavior.
  • CUSTOM_LOCATIONS - location matching, rewrites and local responses.
  • VHOST_ACCESS - access rules applied to vhosts and locations.
  • CACHE - cache behavior and policy.
  • TRANSFORM - response transformation.
  • STREAMS - stream proxying.
  • REDIRECTS - redirect hosts and rules.
  • NOT_FOUND_HOSTS - local 404 host handling.
  • DOCKER_DISCOVERY - Docker discovery and generated vhosts.
  • ACME_PROVIDERS and RENEWAL - certificate automation.
  • LIVE_LOGS, FILE_LOGS and ERROR_LOGGING - independent in-memory live request viewing, bounded on-disk log exploration, protocol-error persistence and optional error-file logging.

Administration and operations

Development and testing

  • MOCK_SERVER - local Python mock origin used by development/integration checks.
  • MOCK_AUTH - local fake Tinyauth peer for development only.
  • MEMORY_STRESS - sustained-memory audit, offline load simulations, real RustProxy staging stress and RSS measurement procedure.

Technical documentation

The pre-cleanup developer-level changelog is retained as CHANGELOG_TECHNICAL_ARCHIVE when low-level historical detail is needed. The root CHANGELOG.md remains the operator-facing release record. Completed roadmap history is retained separately as ROADMAP_HISTORY; the root ROADMAP.md contains the current release scope and future direction.

Historical or version-labelled context

Retained audits and historical context

The old per-version implementation notes and audits removed from this trimmed source archive are no longer required to build the application or use the documentation Reader. Only registered documents are embedded at compile time.

Maintenance rules

  • Put user/operator-visible release changes in CHANGELOG.md.
  • Put future release scope in ROADMAP.md and unresolved work in docs/TODO.md.
  • Keep detailed implementation evidence in technical documents or version audits, not in CHANGELOG.
  • When functionality changes, update the functional document, this index, Reader coverage and cross-links in the same change.
  • Remove obsolete or duplicated documents when they no longer provide historical or technical value; retain useful audits with an explicit historical label.