Trigger.dev

nick0lay
HOBBY

2 months ago

Description: Deploy Trigger.dev v4 complete stack: PostgreSQL, Redis, ClickHouse & more

Category: Automation

URL: https://railway.com/deploy/triggerdev

3 Replies

deuxego
PRO

2 months ago

Hello, first of all, thank you for the template.

I encountered the following problem: I launched your template, launched the worker locally, and am trying to run tasks in production mode. The tasks are being executed, but I can't see them in the “Runs” tab; it's always empty. Do you know what might be causing this?


deuxego

Hello, first of all, thank you for the template.I encountered the following problem: I launched your template, launched the worker locally, and am trying to run tasks in production mode. The tasks are being executed, but I can't see them in the “Runs” tab; it's always empty. Do you know what might be causing this?

nick0lay
HOBBY

2 months ago

Hey,

Thanks a lot for trying out the template and for reporting this!

The issue comes from Postgres → Clickhouse replication not being set up by default. I’m working on making this part of the bootstrap script so it’ll be easier to configure.

There’s also a limitation with Supervisor on Railway since it needs Docker socket access, which Railway doesn’t support yet. I’m testing alternatives (like DigitalOcean) for that part.

I’ll share an update here once both are fixed.


nick0lay
HOBBY

2 months ago

Hey deuxego,

I've just pushed a update that fixes both issues you encountered:

  • Runs now appear in UI - The template now includes automated PostgreSQL → ClickHouse replication setup via the ops-controller, so your task runs will show

up in the dashboard immediately.

  • Supervisor deployment solved - Since Railway doesn't support Docker socket access, the template now uses a dual-platform architecture:

    • Railway: Hosts the webapp, PostgreSQL, Redis, ClickHouse, MinIO and all the other services except supervisor

    • DigitalOcean: Runs the supervisor for actual task execution

How it works now:

  1. Deploy the template (one-click as before)

  2. Add your DigitalOcean and Railway API token to the Railway ops-controller service

  3. The ops-controller automatically provisions and manages a DigitalOcean droplet for task execution

  4. Everything else is handled automatically - no manual setup required

Try the updated template and let me know how it works for you! The "Runs" tab should now populate properly with your task executions.

Thanks for the feedback!