Publish the site as a container on the cluster instead of the pages branch
CI / test (pull_request) Successful in 42s
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>
This commit is contained in:
+3
-3
@@ -13,9 +13,9 @@ branch: main
|
||||
# public, limited (only people signed in to this server) or private: who can open the links below
|
||||
visibility: limited
|
||||
|
||||
# the published page: Ken's server serves the `pages` branch (.gitea/workflows/pages.yml). Set this to its address
|
||||
# once it is up (then `python -m collection build`): the page's links and the dataset metadata use it.
|
||||
site: null
|
||||
# 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:
|
||||
|
||||
Reference in New Issue
Block a user