Hold /privacy behind a flag until counsel reads it, and fix leftover legal and email copy.

This commit is contained in:
adilallo committed 2026-11-20 15:36:06 -07:00
1 parent ead6c8f716
commit 072e5362f5
43 files changed
+548 -191

No files matched your search

+10 -3
View File
@@ -75,8 +75,14 @@ per-app in the manifest and provisioned at install time.
- `SESSION_SECRET` — long random (`openssl rand -hex 32`). Required,
≥ 16 chars. Rotating it logs everyone out.
- `SMTP_FROM` — visible "From:" address on sign-in emails. Cloudron
does not inject this. Use `hello@communityrule.info` (continuity
with the legacy service; SES relay accepts it).
does not inject this. Use `CommunityRule <hello@communityrule.info>`
(continuity with the legacy service; SES relay accepts it). A leftover
`Community Rule` display name is rewritten to one word.
- `ENABLE_PRIVACY_POLICY=true` — turns on `/privacy` at runtime. Staging
keeps this on so counsel can read the page. Leave unset in production
until that review is done (the route 404s and public chrome does not
link to it). `NEXT_PUBLIC_ENABLE_PRIVACY_POLICY` is the same switch
baked at image build; prefer the runtime name on Cloudron.
- `NEXT_PUBLIC_ENABLE_BACKEND_SYNC=true` — turns on Postgres draft
persistence for signed-in users. Required in production.
- `UPLOAD_ROOT` — absolute path to a writable directory on the Cloudron
@@ -444,7 +450,8 @@ production env vars, and verify the vertical slice before apex cutover
```bash
cloudron env set --app staging.communityrule.info \
SESSION_SECRET="$(openssl rand -hex 32)" \
SMTP_FROM="Community Rule <hello@communityrule.info>" \
SMTP_FROM="CommunityRule <hello@communityrule.info>" \
ENABLE_PRIVACY_POLICY=true \
NEXT_PUBLIC_ENABLE_BACKEND_SYNC=true \
UPLOAD_ROOT=/app/data/uploads
```
+3 -2
View File
@@ -246,7 +246,8 @@ persist across image updates unless changed:
| Variable | Purpose |
| -------- | ------- |
| `SESSION_SECRET` | Session cookie signing (≥ 16 chars). Rotating logs everyone out. |
| `SMTP_FROM` | Visible From on sign-in emails (e.g. `Community Rule <hello@communityrule.info>`). |
| `SMTP_FROM` | Visible From on sign-in emails (e.g. `CommunityRule <hello@communityrule.info>`). The app rewrites a leftover `Community Rule` display name to one word. |
| `ENABLE_PRIVACY_POLICY` | `true` on staging so `/privacy` is reachable. Unset in production until counsel has read the policy (404, no public links). |
| `NEXT_PUBLIC_ENABLE_BACKEND_SYNC` | `true` in staging/production — Postgres draft persistence. |
| `UPLOAD_ROOT` | `/app/data/uploads` on Cloudron — required for file uploads. |
| `OPS_PRUNE_TOKEN` | Bearer token for `POST /api/ops/prune`. Unset hides the route. Optional; the daily scheduler runs the prune inside the container without it. |
@@ -283,7 +284,7 @@ That is expected. Recipients still authenticate the visible `From:` (`staging.ap
2. In **Cloudron** → *Domains* → `communityrule.info` → DNS, add those CNAMEs. Cloudron's Namecheap provider publishes them to the registrar. Confirm with `dig +short CNAME <selector>._domainkey.communityrule.info`.
3. Optional but recommended for SPF alignment: add `include:amazonses.com` to the existing TXT SPF, e.g. `v=spf1 include:amazonses.com a:my.medlab.host ~all`. Do not remove `a:my.medlab.host` until you know nothing still sends directly from the box.
4. Leave DMARC at `p=reject` once DKIM verifies in SES; if a provider still quarantines after DKIM is live, inspect that provider's headers before relaxing DMARC.
5. Retest: request a magic link to Gmail **and** a non-Gmail inbox (May First / university). Check spam. Staging From is `Community Rule <staging.app@communityrule.info>`.
5. Retest: request a magic link to Gmail **and** a non-Gmail inbox (May First / university). Check spam. Staging From is `CommunityRule <staging.app@communityrule.info>`.
`SMTP_FROM` should stay the Cloudron mailbox (`staging.app@communityrule.info` on staging, `hello@communityrule.info` on the apex app). The app falls back to `CLOUDRON_MAIL_FROM` if `SMTP_FROM` is unset.
+4 -3
View File
@@ -1,8 +1,8 @@
# Privacy policy facts
Numbers and hosting details the new privacy policy leaves in brackets.
Live `/privacy` stays on the current page until university counsel has
read this text. Do not switch the route on from this file.
Live `/privacy` stays behind `ENABLE_PRIVACY_POLICY` until university
counsel has read this text. Do not switch the route on from this file.
## How long things are kept
@@ -53,6 +53,7 @@ See [`docs/guides/ops-runbook.md`](guides/ops-runbook.md) §9.3.
- `/privacy` can show the new policy only after university counsel has
read it, including the Colorado Open Records Act line, Terms, Cookies,
the legal cards, and CC0 for cards and templates.
the legal cards, and CC0 for cards and templates. Flipping
`ENABLE_PRIVACY_POLICY=true` on production is that switch.
- An email to every account holder before a change to who can read Rules
is after launch. Nothing about who can read Rules changes at launch.