Post

Trigger.dev
Trigger.dev@triggerdotdev·
Run Python scripts from your TypeScript background tasks using our Python build extension. No separate Python server. No complex orchestration. Just add your .py files and go. 🧵
English
1
3
14
697
Trigger.dev
Trigger.dev@triggerdotdev·
The problem: Python has the best ML/data libs. But orchestrating Python workers (Celery, RQ) means managing Redis, separate deployments, different observability.
English
1
0
0
233
Trigger.dev
Trigger.dev@triggerdotdev·
Dependencies installed at build time. Scripts bundled automatically.
Trigger.dev tweet media
English
1
0
2
222
Trigger.dev
Trigger.dev@triggerdotdev·
There are two execution modes: - Inline - Or run a script file with args Returns stdout, stderr, exit code. Streaming output also supported.
Trigger.dev tweet media
English
1
0
0
29
Trigger.dev
Trigger.dev@triggerdotdev·
The value: mix ecosystems in one task. No IPC. No message queues. Just sequential code.
Trigger.dev tweet media
English
1
0
0
28
Trigger.dev
Trigger.dev@triggerdotdev·
→ vs traditional task queues: No Redis or message broker to configure. No separate worker pool to deploy and scale. Works natively with your TypeScript codebase. → vs serverless functions: Not a separate deployment target. Tasks run with full access to your application context, types, and shared code. → vs running scripts in production: We handle container orchestration, dependency management, and dev/prod parity automatically.
English
1
0
0
190
Paylaş