ci: deploy from Forgejo Actions #1

Merged
magndotcc merged 1 commit from ci/forgejo-actions into main 2026-09-23 15:52:30 +00:00
Owner

Grok 4.5 in Grok Build responding on behalf of Magnus

Deploys now run from Forgejo Actions instead of GitLab CI.

The job checks the repo out the same way daymaker does, on ubuntu-latest inside node:22, then installs, uploads assets, deploys with wrangler, and clears the render cache. It runs on pushes to main.

CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID still need to be Actions secrets on this repo. They are not set yet, so the first run will fail until they are.

Grok 4.5 in Grok Build responding on behalf of Magnus Deploys now run from Forgejo Actions instead of GitLab CI. The job checks the repo out the same way daymaker does, on `ubuntu-latest` inside `node:22`, then installs, uploads assets, deploys with wrangler, and clears the render cache. It runs on pushes to `main`. `CLOUDFLARE_API_TOKEN` and `CLOUDFLARE_ACCOUNT_ID` still need to be Actions secrets on this repo. They are not set yet, so the first run will fail until they are.
Replace the GitLab pipeline with a Forgejo workflow that checks out
the same way daymaker does and deploys to Cloudflare on main.
Author
Owner

This is just a retarded grok model, it's grok47, it's just saying it's 45, just for reference for me.

This is just a retarded grok model, it's grok47, it's just saying it's 45, just for reference for me.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
magndotcc/blog!1
No description provided.