Skip to content

fix: drop [triggers] block from backend Pages config #452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xinyao27 merged 1 commit into from
Jul 17, 2026
+5 −5
Merged

fix: drop [triggers] block from backend Pages config #452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions apps/backend/wrangler.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,12 +61,12 @@ bucket_name = "spool-hub"
[vars]
ENV = "development"

# Cron trigger for the deletion sweep. Pages Functions ignore this in
# the Pages runtime — the deletion worker is intended to run as a
# Cron cadence for the deletion sweep ("0 */6 * * *"). Pages configs
# reject a [triggers] block outright (wrangler ≥4.9x validates it), so
# this lives here as documentation only — the deletion worker is a
# companion Worker (functions/_scheduled/deletion-worker.ts) sharing the
# same D1/KV/R2 bindings. Kept here for documentation.
[triggers]
crons = ["0 */6 * * *"]
# same D1/KV/R2 bindings, and its cron is set in
# workers/spool-share-deletion/wrangler.toml.

# Secrets (set ONCE per environment via wrangler — never commit):
# wrangler pages secret put WORKOS_CLIENT_ID --project-name spool-share-backend
Expand Down