Every push to main now builds the Atlas page into an nginx image and pushes it to harbor.kenschiano.net/home/threshing-atlas:latest (.gitea/workflows/image.yml).
Argo CD Image Updater picks up the new digest and rolls the deployment in kubefiles
(web/threshing-atlas), served at https://threshingatlas.kenschiano.net. The site is already live from a
manually pushed image; this makes merges keep it current.
Dockerfile + deploy/nginx.conf: node builds the site, unprivileged nginx serves it on 8080 (/healthz for probes)
Removes .gitea/workflows/pages.yml (the pages branch is no longer served)
forge.yamlsite: and data/croissant.jsonurl point to the new address
Before merging: add repo or org secrets HARBOR_USERNAME and HARBOR_PASSWORD (a Harbor robot account with push access to the home project), or the image workflow will fail.
Every push to main now builds the Atlas page into an nginx image and pushes it to
`harbor.kenschiano.net/home/threshing-atlas:latest` (`.gitea/workflows/image.yml`).
Argo CD Image Updater picks up the new digest and rolls the deployment in kubefiles
(`web/threshing-atlas`), served at https://threshingatlas.kenschiano.net. The site is already live from a
manually pushed image; this makes merges keep it current.
- `Dockerfile` + `deploy/nginx.conf`: node builds the site, unprivileged nginx serves it on 8080 (`/healthz` for probes)
- Removes `.gitea/workflows/pages.yml` (the `pages` branch is no longer served)
- `forge.yaml` `site:` and `data/croissant.json` `url` point to the new address
**Before merging:** add repo or org secrets `HARBOR_USERNAME` and `HARBOR_PASSWORD` (a Harbor robot account with push access to the `home` project), or the image workflow will fail.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Every push to main builds the page into an nginx image and pushes it to
harbor.kenschiano.net/home/threshing-atlas; Argo CD Image Updater rolls the
deployment (kubefiles web/threshing-atlas) at https://threshingatlas.kenschiano.net.
forge.yaml now names that address.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Node build on hi/nodejs:22-builder, the nginx config checked with `nginx -t` on
hi/nginx:latest-builder, served by the distroless hi/nginx runtime (UID 65532,
no shell). nginx keeps temp files in /tmp so the pod can run with a read-only
root filesystem; adds nosniff/referrer headers and hides the nginx version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every push to main now builds the Atlas page into an nginx image and pushes it to
harbor.kenschiano.net/home/threshing-atlas:latest(.gitea/workflows/image.yml).Argo CD Image Updater picks up the new digest and rolls the deployment in kubefiles
(
web/threshing-atlas), served at https://threshingatlas.kenschiano.net. The site is already live from amanually pushed image; this makes merges keep it current.
Dockerfile+deploy/nginx.conf: node builds the site, unprivileged nginx serves it on 8080 (/healthzfor probes).gitea/workflows/pages.yml(thepagesbranch is no longer served)forge.yamlsite:anddata/croissant.jsonurlpoint to the new addressBefore merging: add repo or org secrets
HARBOR_USERNAMEandHARBOR_PASSWORD(a Harbor robot account with push access to thehomeproject), or the image workflow will fail.🤖 Generated with Claude Code