4 Commits

Include renames

Author	SHA1	Message	Date
haemka	33654a1030	Use SSH deploy key instead of account token for theme submodule ... Avoids tying CI to a personal/bot Gitea account: the same DEPLOY_SSH_KEY secret used for the webserver rsync step is reused as a read-only Gitea deploy key on hmk/pelican-latex. The submodule's tracked HTTPS URL is overridden to SSH just for this checkout so it authenticates with that key instead of needing a token with access to both repos.	2026-08-13 15:13:44 +00:00
haemka	387a53d37c	Pass explicit token to checkout for private theme submodule ... The default per-job Actions token only covers the triggering repo; the theme submodule lives in a separate private repo (hmk/pelican-latex), so cloning it needs a token with read access to both. Add CHECKOUT_TOKEN as a repo secret (a Gitea access token with repo read scope) for this to work.	2026-08-13 15:08:26 +00:00
haemka	88bed173c1	Install nodejs in workflow container so actions/checkout can run ... python:3.12-slim has no Node.js; JS-based actions like actions/checkout need it to execute their bundled dist/index.js.	2026-08-13 15:03:49 +00:00
haemka	d47300a4d7	Add Gitea Actions workflow to build and deploy the site ... Requires a self-hosted runner and repo secrets (DEPLOY_HOST, DEPLOY_USER, DEPLOY_PATH, DEPLOY_SSH_KEY) to be set up before it will actually run.	2026-08-13 14:46:19 +00:00