wtclaude
f2e59a2426
All checks were successful
PR checks / checks (pull_request) Successful in 9m46s
PLAN.md §13 phase 12, the last one. Four decisions of record, D54–D57, taking the count to fifty-seven; recorded in §6, "How phase 12 delivered it". A two-stage Dockerfile, a pull-only docker-compose.yml carrying both bind mounts, .env.example, the workflow that publishes and deploys, CONTRIBUTING.md, the community-health files this was the only repository of the ten to lack, and DEPLOY.md. D54 — a merge deploys, amending D6. build-image.yml pushes runicgateway-site:latest and :sha-<7>, then rolls the container over on the `rgcom` runner out of /opt/runicgateway.com, and waits for the container's own healthcheck rather than for `up -d` to return. D55 — the site runs on its own host behind a generic reverse proxy, so DEPLOY.md states the four requirements rather than one worked example, and the container binds 127.0.0.1 so the safe configuration is the default. D56 — @astrojs/node derives the request protocol from req.socket.encrypted and never reads x-forwarded-proto, so behind a TLS-terminating proxy the browser sends Origin: https://… while the container computes http://… and Astro's CSRF check compares them for equality. Every beta signup, from every visitor, was answered 403. serve.mjs now normalises both forwarded headers, unconditionally — the image should deploy and work. Two assertions in test/headers.test.mjs hold both halves. D57 — DEPLOY.md rather than a README section; SECURITY.md and CODE_OF_CONDUCT.md are pointers to the org's copies rather than copies, because a copy would hard-code the contact address D13 confines to brand.json. Verified: npm run verify green (eleven checks, 36 unit tests, 7 served tests, astro check 0 errors). The image was built and run with both mounts — a mounted brand reached 51 files and all 50 search pages, /brand/* fell back per file, a proxy-shaped signup reached the store, and the export CLI wrote both Play files to the host mount. docker compose config caught a YAML trap in the healthcheck: a block sequence reads the `: ` in `r.ok ? 0 : 1` as a mapping. Co-Authored-By: Claude <noreply@anthropic.com>
49 lines
1.3 KiB
Markdown
49 lines
1.3 KiB
Markdown
---
|
|
name: Bug report
|
|
about: Something on the site is broken, wrong, or behaving unexpectedly
|
|
title: "[bug] "
|
|
labels:
|
|
- bug
|
|
---
|
|
|
|
## Summary
|
|
|
|
<!-- A clear, concise description of the problem. -->
|
|
|
|
## Where
|
|
|
|
<!-- The URL, or the page and the section. If it is a documentation page, the heading. -->
|
|
|
|
- Page:
|
|
- Viewport width, if it is a layout problem:
|
|
- Browser and version:
|
|
|
|
## What happened, and what you expected
|
|
|
|
<!--
|
|
Include exact wording for a factual error, and the console message if there is
|
|
one. A screenshot helps for anything visual.
|
|
-->
|
|
|
|
## Is it a factual error?
|
|
|
|
<!--
|
|
The most valuable reports this repository gets are claims that are WRONG about
|
|
the platform — a version, a command, a flag, a capability that no longer works
|
|
that way. If so, say where the correct answer lives (which repository, which
|
|
file), because the fix is usually to a data file or a check rather than to the
|
|
sentence.
|
|
-->
|
|
|
|
## Additional context
|
|
|
|
<!-- Anything else that helps. -->
|
|
|
|
<!--
|
|
Security issue? Do NOT file it here — see SECURITY.md for the private route.
|
|
|
|
A problem with the PLATFORM rather than with this site (the website, the
|
|
sidecar, the shard plugin, the installer, the Android app) belongs in that
|
|
repository's tracker. This one only describes them.
|
|
-->
|