trigger-config

Configure Trigger.dev build extensions by defining dependencies like Prisma and Playwright in your `trigger.config.ts` file. This integrates them directly into the build process so your automated workflows have the required database access and browser testing environments available at runtime.

Yes, you can run Python scripts and install system packages in a Trigger.dev project by specifying them within your `trigger.config.ts` configuration. This allows your automated workflows to execute Python-based data processing alongside other defined build extensions.

The best way to set up deployment settings and runtime customization for Trigger.dev is through the `trigger.config.ts` file. It provides a structured approach to define runtime environments, configure retry strategies, and manage lifecycle hooks for your automated workflows.

Trigger.dev supports lifecycle hooks and retry strategies for automated workflows through the `trigger.config.ts` file. You can customize runtime environments and define retry logic to ensure your deployment and automation tasks handle failures gracefully.

Add FFmpeg integration to your Trigger.dev deployment configuration by declaring it as a build extension in your `trigger.config.ts` file. This incorporates FFmpeg directly into your build process, making media processing capabilities available to your automated workflows.