docs: add Node and Bun process worker deployment guide#630
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
View your CI Pipeline Execution ↗ for commit 34377ec
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
5d91440 to
ab81d38
Compare
e05006e to
475fe79
Compare
|
|
475fe79 to
e27f093
Compare
ab81d38 to
6ac3f60
Compare
e27f093 to
eae2d01
Compare
6ac3f60 to
34cbcd8
Compare
eae2d01 to
34377ec
Compare
🔍 Preview Deployment: Website✅ Deployment successful! 🔗 Preview URL: https://pr-630.pgflow.pages.dev 📝 Details:
_Last updated: _ |

Adds documentation and navigation for deploying pgflow workers as long-running Node or Bun processes on hosts like Railway, Fly, Docker, or VMs.
The new guide covers installing the npm package, writing a worker script, required environment variables (
DATABASE_URL,SUPABASE_URL,SUPABASE_SERVICE_ROLE_KEY), running the worker under Node or Bun, graceful shutdown behavior onSIGTERM/SIGINT/SIGQUIT, health monitoring via database queries, and how process workers differ from HTTP-started workers in thatensure_workers()does not restart them.The deploy overview page and sidebar navigation are updated to include the new guide, the Supabase deployment page gains a callout pointing process-hosted deployments to the new guide, and the
edge-workerREADME replaces its JSR-only warning with a note that the package is published to both JSR and npm with guidance on which to use for each runtime.