Compare commits

...

2 Commits

Author SHA1 Message Date
patrick 19f1ab3996 fix: remove deprecated link property from project template
Generate a build and push to Cloudflare Pages / Build and Deploy to Cloudflare Pages (push) Successful in 1m27s
2026-05-14 13:34:11 -04:00
patrick 98dbf0e885 content: fix error in CF Pages CI/CD post
Generate a build and push to Cloudflare Pages / Build and Deploy to Cloudflare Pages (push) Failing after 46s
Update the post to mention that the Cloudflare Pages project should
exist before running the workflow - the wrangler action does not create
it as previously stated.
2026-05-14 13:21:58 -04:00
2 changed files with 7 additions and 4 deletions
+2 -1
View File
@@ -24,9 +24,10 @@ const projects = defineCollection({
description: z.string(),
tags: z.array(z.string()),
image: image(),
link: z.string().url().optional(),
links: z.array(z.object({
label: z.string(),
url: z.url()
url: z.string().url()
})).optional(),
order: z.number().optional(),
startDate: z.coerce.date().optional(),
+5 -3
View File
@@ -24,6 +24,7 @@ Before getting started, you'll need:
- A Gitea instance with Actions enabled ([documentation](https://docs.gitea.com/usage/actions/overview))
- A registered Gitea runner (ubuntu-latest or equivalent)
- A Cloudflare account with access to Pages
- An existing Cloudflare Pages project
- Your project set up with pnpm (adjust commands for npm/yarn as needed)
---
@@ -74,6 +75,10 @@ jobs:
command: pages deploy ./dist --project-name="your-project-name"
```
> [!WARNING]
> If your Cloudflare Pages project doesn't exist yet, create it before running the workflow, otherwise it will fail.
The workflow triggers on pushes to `main`, installs dependencies, builds the site, and deploys using Cloudflare's Wrangler action. Every push to main goes straight to production.
> [!NOTE]
@@ -83,9 +88,6 @@ The workflow triggers on pushes to `main`, installs dependencies, builds the sit
## Required Secrets
> [!TIP]
> If your Cloudflare Pages project doesn't exist yet, Wrangler will create it automatically on the first deployment.
You'll need to configure two secrets in your Gitea repository (Settings → Actions → Secrets):
- `CLOUDFLARE_API_TOKEN` — Create this in the Cloudflare dashboard: Profile → API Tokens → Create Token → Use the "Edit Cloudflare Pages" template (or create a custom token with **Account: Cloudflare Pages: Edit** permission)