Show HN: Apcher – Generate self-hosted Node.js workflows from prompts

Re:Show HN: Apcher – Generate self-hosted Node.js workflows ... by guerython on Tuesday March 03, 2026 @01:13PM (#47236375)

nice to see prompt-to-node automation getting some love. when we tried something similar we treated the generated flow as code: we wrap it in a type-safe template, lint it, and run fixture-based checks before shipping. curious how apcher manages secrets/env config and how you prove the generated pipeline actually works before importing it?

[ Parent | on HN ]

Re:Show HN: Apcher – Generate self-hosted Node.js workflows ... by Samueedwards1 on Tuesday March 03, 2026 @01:24PM (#47236533)

Great question—we treat generated code as production code too.

Secrets/Env: - `${{ secrets.YOUR_SECRET }}` GitHub Actions syntax throughout - `.env.example` + docker-compose.yml with all expected vars - No hardcoded values; all externalized

Proving it works: - Built-in fixture tests (`npm test`) for every integration point - `npm run apcher:full-scan` catches CVEs + dep issues pre-ZIP - Watchdog generates synthetic drift tests that run on startup - Idempotency baked in (safe to retry 1K times)

Example ZIP includes Stripe test mode keys + Postgres docker fixture.

[ Parent | on HN ]