CI / test (pull_request) Successful in 42s
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>
23 lines
1.3 KiB
YAML
23 lines
1.3 KiB
YAML
# Where the Atlas's repository is hosted. Everything that talks to the host reads this file: the daily workflow
|
|
# (opening its pull request and issues), the "Report a run" collector, the links on the page and in the dataset
|
|
# metadata (data/croissant.json). Moving hosts is an edit here (then `python -m collection build`).
|
|
#
|
|
# kind: gitea or github. The Gitea workflows live in .gitea/workflows/ (Gitea ignores .github/workflows/ when that
|
|
# folder exists); the GitHub ones, including GitHub Pages, stay in .github/workflows/ for when GitHub is used again.
|
|
version: 1
|
|
|
|
kind: gitea
|
|
url: https://git.kenschiano.net
|
|
repo: DragonKind/threshing-atlas # owner/name on the server (the DragonKind organization, beside the bot's repo)
|
|
branch: main
|
|
# public, limited (only people signed in to this server) or private: who can open the links below
|
|
visibility: limited
|
|
|
|
# the published page: a container on Ken's cluster (.gitea/workflows/image.yml, kubefiles web/threshing-atlas). Its address
|
|
# (after a change, `python -m collection build`): the page's links and the dataset metadata use it.
|
|
site: https://threshingatlas.kenschiano.net
|
|
|
|
# other copies of the repository (informational)
|
|
mirrors:
|
|
github: https://github.com/ekcSchiano/threshing-atlas # suspended; GitHub Pages workflow kept for later
|