generated from john/python-template
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# Cloudflare Tunnel and Access Setup (V6.0 Phase 3)
|
||||
# Cloudflare Tunnel and Access Setup
|
||||
|
||||
This guide defines the repository-supported setup for exposing app and selected LAN services through Cloudflare Tunnel with Cloudflare Access protection.
|
||||
|
||||
|
||||
+3
-3
@@ -26,9 +26,9 @@ This directory is the single source of truth for current V6.1 behavior and archi
|
||||
|
||||
## Baseline Statement
|
||||
|
||||
The current V6.1 baseline includes behavior delivered through the architectural cleanup phases and
|
||||
person-schema redesign (through V5.1), the V6.0 hosting migration to a containerized PostgreSQL
|
||||
deployment, and the V6.1 navigation, Document Detail, and worker-backed maintenance refinements.
|
||||
The current V6.1 baseline includes the architectural cleanup, person-schema redesign,
|
||||
containerized PostgreSQL deployment, and the navigation, Document Detail, and worker-backed
|
||||
maintenance refinements reflected across this canonical document set.
|
||||
Use this `docs/*` canonical set for active design and implementation decisions.
|
||||
|
||||
Every canonical document above states this same baseline; `tests/test_meta_contract_guards.py`
|
||||
|
||||
@@ -20,7 +20,7 @@ This runbook is the operational checklist for releasing and monitoring the trans
|
||||
## 2. Release execution steps
|
||||
|
||||
1. Deploy artifact/config to target environment.
|
||||
- V6.0 Phase 1 production stack: `docker compose -f docker-compose.production.yml up -d --build`
|
||||
- Production stack: `docker compose -f docker-compose.production.yml up -d --build`
|
||||
- `Settings` loads from explicit `_env_file`, then `ENV_FILE`, then the repository-root `.env.production`; it does not resolve relative to the process working directory.
|
||||
- For Runtime Settings writes in production, mount `.env.production` into the app container and set `RUNTIME_SETTINGS_ENV_FILE=/app/.env.production`.
|
||||
- If deployment uses a non-default env-file location, set both `ENV_FILE` and `RUNTIME_SETTINGS_ENV_FILE` to that absolute path so startup reads and Settings-page writes stay aligned.
|
||||
|
||||
@@ -146,5 +146,5 @@ Rules:
|
||||
|
||||
## Known Limitations and Deferred Work
|
||||
|
||||
- Source page ordering remains read-only in V4.4.
|
||||
- Source page ordering remains read-only.
|
||||
- Printing other entities, batch printing, and server-side export formats are deferred.
|
||||
|
||||
@@ -96,4 +96,4 @@ The list accepts optional `document_id` and `job_id` query parameters. Document
|
||||
|
||||
## Planned Changes
|
||||
|
||||
- Source page reordering is deferred beyond V4.3 and may be reconsidered if a demonstrated workflow need emerges.
|
||||
- Source page reordering remains deferred unless a demonstrated workflow need emerges.
|
||||
|
||||
Reference in New Issue
Block a user