Matt Aitken
de302858f8
* Started building out the docs navigation * Drafted out a lot of the docs pages. With just titles and descriptions with a coming soon message for now. * A ton more scaffolded pages with titles, descriptions, coming soon/incomplete docs messages * Created the remaining page stubs * Introduction page improvements * Lots of docs changes, mostly the task overview page * Moved some bits around * Task overview fleshed out * Triggering docs page * Regular task page * CLi dev docs * Docs for debugging locally * Environment variables docs * Added env var images * Deployment guides * Updated the title of “Integrations” to “Deployment integrations” to make it less confusing * Lots more docs pages * Changed the language to JavaScript * Fixed typos about queues and added a simple code sample * Moved the local debugger docs into the CLI dev page * Added the CLI deploy options * Delete the local debugger page * Updated the logging page with structured logging * Added the new CLI deploy options * Change to h4 for one of the options * Errors page * WIP on retrying * Retrying guide * Wait docs pages * Queuing docs simplified, partial written * Queuing and concurrency docs * Run tests docs * New combined error and retrying page * Errors and retrying page updated * More docs * Added a possible configurations coming soon table * Created a limits page * Added warnings about how you need to get early access * Minor fixes for the docs
26 lines
960 B
Plaintext
26 lines
960 B
Plaintext
---
|
|
title: "/trigger folders"
|
|
description: "Your tasks live inside /trigger folders. Code in these is bundled and deployed together."
|
|
---
|
|
|
|
## What gets bundled?
|
|
|
|
We automatically bundle everything for your tasks. This includes:
|
|
|
|
- Your tasks (they can be in any file inside a /trigger folder, they just need to be exported with a name).
|
|
- Imported npm packages.
|
|
- Other imports from your code.
|
|
|
|
This means you shouldn't need to think about what gets bundled. Just write your tasks and we'll take care of the rest.
|
|
|
|
## Multiple `/trigger` folders
|
|
|
|
You can have multiple `/trigger` folders in your repository.
|
|
|
|
- Each `/trigger` folder can have many tasks exported from it.
|
|
- Each file inside a `/trigger` folder can export many tasks.
|
|
|
|
### (Optional) configuration
|
|
|
|
It is possible to manually set one or more folders as `/trigger` folders in your `trigger.config` file. View the [trigger.config documentation](/v3/referece-trigger-config) for more information.
|