Trigger.dev - Open-source background jobs for NextJS, Remix, Astro,
and many more!
reddit / selfhosted

----------------------------------------------------------------------
Alternative-Rich-578 · 2023-10-03 11:32

Hi guys!

Last time, our post got blocked, claiming we are not open-source.

TriggerDev is 100% open-source (all the features, everything) :)

​

Please feel free to check us out here:

[https://github.com/triggerdotdev/trigger.dev](https://github.com/trig
gerdotdev/trigger.dev)

​

For the self-hosting tutorial, visit:

[https://github.com/triggerdotdev/docker](https://github.com/triggerdo
tdev/docker)

​

Here are some use cases with things you can do with TriggerDev:

[https://trigger.dev/blog/generator-unlocked-create-memes-with-
chatgpt-and-nextjs](https://trigger.dev/blog/generator-unlocked-
create-memes-with-chatgpt-and-nextjs)

[https://tgr.dev/achieve-nextjs-mastery-build-a-sales-page-with-
stripe-and-airtable](https://tgr.dev/achieve-nextjs-mastery-build-a-
sales-page-with-stripe-and-airtable)

----------------------------------------------------------------------
anrikaz · 2023-10-03 12:12

Looks pretty solid. I'm going to try it tonight!

----------------------------------------------------------------------
zn448sk39 · 2023-10-03 14:08

Can I replace bullmq with this? And how does it work? The readme
didn't really explain that. Are you just pinging my api urls?

----------------------------------------------------------------------
matt-aitken · 2023-10-03 14:50

Yep you can replace BullMQ with this, if you're deploying to a
serverless environment. We're going to add long-running server support
soon and support for edge (Cloudflare/Deno). That will mean you can
use it anywhere that you can deploy JavaScript.
We need to add a better explanation in our readme on how it works, and
the homepage of the site. In short we create a secured API endpoint on
your service that can receive messages. It's basically an API/SDK that
allows you to write code that looks like normal async code, but when
you use tasks, wait, built-in retries, etc we handle doing all of that
reliably. For serverless we also allow you to write long jobs without
hitting timeouts, providing you divide your work into chunks using
tasks/the integrations.

There's a blog post here which does into a lot of detail of how it
works: https://trigger.dev/blog/deep-dive-how-trigger-makes-
background-jobs-easy

----------------------------------------------------------------------
zn448sk39 · 2023-10-03 15:09

> We're going to add long-running server support soon

Is there an issue on this I can follow? We don't run serverless

> There's a blog post here which does into a lot of detail of how it
works: https://trigger.dev/blog/deep-dive-how-trigger-makes-
background-jobs-easy

Thank you!

----------------------------------------------------------------------
matt-aitken · 2023-10-03 15:17

Yep, the issue is here: [https://github.com/triggerdotdev/trigger.dev/
issues/244](https://github.com/triggerdotdev/trigger.dev/issues/244)


It links to [this discussion](https://github.com/triggerdotdev/trigger
.dev/discussions/430) which details how we're thinking of structuring
the SDK experience. Feel free to weigh in with any thoughts.