Jean-Luc Makiola
cecbda26b0
Gate blog listings/RSS on pubDate<=now (in addition to !draft) via a shared getPublishedPosts() helper, so a post set to draft:false with a future pubDate publishes itself once a build runs on that day. Dev shows everything for preview. Add .gitea/workflows/scheduled-deploy.yml: a daily cron that pings the Coolify deploy hook so the static site rebuilds and the date gate advances. No file mutation, no repo write access — needs a runner + COOLIFY_DEPLOY_HOOK secret. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
50 lines
2.1 KiB
YAML
50 lines
2.1 KiB
YAML
# Daily rebuild so date-scheduled posts go live on their pubDate.
|
|
#
|
|
# The site is static, so "now" is frozen at build time. This cron triggers a
|
|
# fresh Coolify deploy once a day; the rebuild re-evaluates the pubDate gate in
|
|
# src/utils/posts.ts, and any post whose date has arrived (and draft: false)
|
|
# appears. No file is mutated and no repo write access is needed — the job only
|
|
# pings the deploy hook.
|
|
#
|
|
# Setup (once):
|
|
# - A Gitea Actions runner must be registered and online for this repo/org,
|
|
# advertising a label that matches `runs-on` below (default act_runner maps
|
|
# `ubuntu-latest`; change it if your runner uses a different label).
|
|
# - Add a repo secret COOLIFY_DEPLOY_HOOK = the app's deploy URL from Coolify
|
|
# (app → Webhooks → "Deploy Webhook", e.g.
|
|
# https://coolify.example.com/api/v1/deploy?uuid=<uuid>&force=false).
|
|
# - Add a repo secret COOLIFY_TOKEN = a Coolify API token (Bearer) with deploy
|
|
# permission. Required for the /api/v1/deploy endpoint.
|
|
#
|
|
# Your normal push-to-main deploy still runs independently; this only covers the
|
|
# "a new day rolled over" case. Trigger it by hand from the Actions tab (this
|
|
# workflow has workflow_dispatch) to smoke-test before relying on the cron.
|
|
|
|
name: scheduled-deploy
|
|
|
|
on:
|
|
schedule:
|
|
# 06:15 Europe/Berlin daily. Posts are eligible from 00:00 UTC on their
|
|
# pubDate; this morning rebuild publishes them. Adjust the time to taste.
|
|
- cron: 'TZ=Europe/Berlin 15 6 * * *'
|
|
workflow_dispatch: {}
|
|
|
|
jobs:
|
|
trigger-deploy:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Ping Coolify deploy hook
|
|
env:
|
|
COOLIFY_DEPLOY_HOOK: ${{ secrets.COOLIFY_DEPLOY_HOOK }}
|
|
COOLIFY_TOKEN: ${{ secrets.COOLIFY_TOKEN }}
|
|
run: |
|
|
if [ -z "$COOLIFY_DEPLOY_HOOK" ]; then
|
|
echo "COOLIFY_DEPLOY_HOOK secret is not set." >&2
|
|
exit 1
|
|
fi
|
|
# Coolify's /api/v1/deploy endpoint is a GET authenticated with a
|
|
# Bearer token. -f makes curl exit non-zero on HTTP errors.
|
|
curl -fsS -X GET "$COOLIFY_DEPLOY_HOOK" \
|
|
${COOLIFY_TOKEN:+-H "Authorization: Bearer $COOLIFY_TOKEN"}
|
|
echo "Deploy triggered."
|