Files
PiCloud/examples/cms-poc/scripts/workflow/wf_publish.rhai
MechaCat02 813bc46640
Some checks failed
CI / Rust — fmt, clippy, test (push) Failing after 39m53s
CI / Dashboard — check (push) Successful in 10m15s
docs(examples): add the CMS proof-of-concept dogfooding artifact
A WordPress-inspired CMS whose entire backend is PiCloud Rhai scripts
deployed with pic apply, plus a SvelteKit frontend. Built to dogfood the
project tool, CLI, and SDK; exercises docs/kv/files/users, docs+queue+cron
+pubsub triggers, the transactional-outbox notification chain, a docs
before-interceptor, set_if CAS, SSE, per-app CORS, env overlays, and a
durable Workflow (validate -> enrich || seo -> publish -> finalize) started
with workflow::start and polled with workflow::run_status, visualized live
with Svelte Flow.

FINDINGS.md / SECURITY.md capture every gap, surprise, and security issue
found (each tagged [PiCloud] vs [CMS]); the platform fixes for the
actionable ones ship in the preceding commit.

Also folds in the read-only `pic` allowlist entries added to
.claude/settings.json during the session (fewer-permission-prompts).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-19 20:15:29 +02:00

14 lines
530 B
Plaintext

// workflow step: publish — flip the post to published. This docs::update fires
// the existing posts_on_publish trigger → queue → reader notification emails,
// so the workflow chains into the rest of the CMS event graph.
let b = ctx.request.body;
let posts = docs::collection("posts");
let post = posts.get(b.post_id);
let d = post.data;
if d.status != "published" {
d.status = "published";
if d.publish_at == () { d.publish_at = time::now(); }
posts.update(b.post_id, d);
}
#{ published: true, slug: d.slug }