Files
RustProxy/docs
2026-10-11 12:21:26 +02:00
..
2026-10-03 00:27:09 +01:00
2026-10-07 13:40:21 +02:00
2026-10-04 09:29:10 +02:00
2026-10-10 23:41:54 +02:00
2026-10-10 20:56:36 +02:00
2026-10-07 22:22:54 +02:00
2026-10-10 00:18:06 +02:00
2026-10-10 20:56:36 +02:00
2026-10-10 21:48:39 +02:00
2026-10-08 22:22:46 +02:00
2026-10-10 00:18:06 +02:00
2026-10-07 09:15:21 +02:00
2026-10-09 17:09:41 +02:00
2026-10-10 08:53:55 +02:00
2026-10-07 22:22:54 +02:00
2026-10-10 20:56:36 +02:00
2026-10-10 21:48:39 +02:00
2026-10-11 12:21:26 +02:00
2026-10-08 22:22:46 +02:00
2026-10-04 09:29:10 +02:00
2026-10-05 17:05:06 +02:00
2026-10-04 09:29:10 +02:00
2026-10-10 08:53:55 +02:00
2026-10-08 11:27:18 +02:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-07 22:22:54 +02:00
2026-10-10 00:18:06 +02:00
2026-10-10 00:18:06 +02:00
2026-10-05 17:05:06 +02:00
2026-10-11 12:21:26 +02:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-08 11:27:18 +02:00
2026-10-07 22:22:54 +02:00
2026-10-08 10:36:34 +02:00
2026-10-10 20:56:36 +02:00
2026-10-03 00:27:09 +01:00
2026-10-06 23:54:01 +02:00
2026-10-10 20:56:36 +02:00
2026-10-03 00:27:09 +01:00
2026-10-11 12:21:26 +02:00
2026-10-04 09:29:10 +02:00
2026-10-09 13:11:33 +02:00
2026-10-08 11:27:18 +02:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-07 22:22:54 +02:00
2026-10-03 00:27:09 +01:00
2026-10-03 00:27:09 +01:00
2026-10-07 22:22:54 +02:00
2026-10-07 22:22:54 +02:00
2026-10-03 10:36:30 +02:00
2026-10-07 22:22:54 +02:00
2026-10-07 22:22:54 +02:00
2026-10-07 22:22:54 +02:00
2026-10-04 16:47:24 +02:00
2026-10-04 22:53:33 +02:00
2026-10-04 23:13:27 +02:00
2026-10-05 09:30:21 +02:00
2026-10-05 19:05:55 +02:00
2026-10-05 22:29:54 +02:00
2026-10-06 10:16:16 +02:00
2026-10-06 11:29:34 +02:00
2026-10-06 11:56:10 +02:00
2026-10-07 22:22:54 +02:00
2026-10-06 23:54:01 +02:00
2026-10-07 09:15:21 +02:00
2026-10-07 13:40:21 +02:00
2026-10-07 22:22:54 +02:00
2026-10-08 09:42:10 +02:00
2026-10-08 09:42:10 +02:00
2026-10-08 10:36:34 +02:00
2026-10-08 11:27:18 +02:00
2026-10-08 15:59:37 +02:00
2026-10-08 22:22:46 +02:00
2026-10-06 15:12:59 +02:00
2026-10-10 00:18:06 +02:00
2026-10-10 00:18:06 +02:00

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

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

Historical or version-labelled context

Version-labelled V*.md files are retained as historical implementation/audit records. Their version number describes the audited milestone. The current release implementation note is IMPLEMENTATION_0.31.3.md; IMPLEMENTATION_0.31.1.md is retained as the prior mobile milestone; IMPLEMENTATION_0.31.0.md is retained as the previous milestone; V0.29.1_IMPLEMENTATION.md is retained as historical context, and V0.29.0_IMPLEMENTATION.md is retained as the prior redirect/health/cache/log milestone; V0.28.2_IMPLEMENTATION.md is retained as the prior certificate-hardening milestone; V0.28.1_IMPLEMENTATION.md is retained as the prior external-path milestone; V0.28.0_IMPLEMENTATION.md is retained as the prior GeoIP/listener/cache milestone, and V0.27.3_IMPLEMENTATION.md is retained as the prior HTTP/3/cache-maintenance milestone, V0.27.2_IMPLEMENTATION.md is retained as the prior managed-ACME repair, V0.27.1_IMPLEMENTATION.md as the prior managed-runtime/list-sorting milestone, and older version notes remain historical evidence. The latest retained audit is V0.25.5_AUDIT.md; older audit files remain available for traceability.

Older context documents such as INTEGRATIONS_040, MANAGEMENT, SECURITY_AUDIT, ACME_RFC2136 and older version audits remain available for traceability but should not override the current functional/technical documents above.

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.

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.