James Ritchie
65fa8300ad
* Removed next references in the ReadMe * FAQ improvements to update Next.js references * Added a new Frameworks page with logos to link to the quick start guides * Renamed the mdx file so the link works * Added basic platform guides * Introduction doesn’t reference next.js only * Added a note about serverless and restructured the side menu * Added more frameworks pages to the manual install section * Fixed SVG error * Coming soon guides now using snippets so they can be in 2 places while we work on them * Removed redirects * Added a new named icon * increased fireworks particle count slightly * Creating a route for the onboarding and link to access it anytime from the side menu * Moved the onboarding into new components * Updated the routes for the onboarding page * Onboarding is now Setup and the frameworks overview page now links to different framework page in the onboarding side nav * URLs and pages renamed to ‘setup’ * URLs and pages renamed to ‘setup’ * Fixed some old named component imports * WIP on a new less hacked-in background image * Added svg logos for all the frameworks * New paths for the new framework pages * Side menu collapses once you selected a framework * Temporary Nuxt page * New routes for the new frameworks * New ‘framework coming soon’ component - now used in the coming soon framework pages * Moved/removed files * Moved all svg framework logos into a new folder and file * balanced the logo sizes * Framework coming soon pages take a name and url * New express svg logo * New component for a Framework item in the grid * Added information and design for the coming soon frameworks * Change the grid to 1 row if jobs === 0 * Updated the framework coming soon snippet and added it to the relevant pages * Express now 2nd in all lists * Added link to long running server support discussion * New logo to include next.js + supabase quick start * roadmap now links to homepage with page anchor to roadmap section * changelog now links to Github releases page * Removed reference to Next.js * Docs pages with coming soon info all share the same framework snippets * Fixed issue of missing props * Moved the fireworks effect into a separate file to make it easier for adding more framework onboarding pages * Info callouts have a more muted style * Added a callout to the top of the next onboarding to reference Serverless-only support * Moved the callout explaining scheduled triggers not working in dev to the bottom of the test panel This is to resolve eric’s UX ticket: https://github.com/triggerdotdev/trigger.dev/issues/416 * Added groundwork for Nest.js framework * Using framer motion for the menu transition instead of css - now has a slight spring and is snappier * redirect the manual setup page to the new nextjs setup page * Fixed broken docs link * Added a readme.md to next.js package * Capital I for integration * Renamed component: NextDevCommand to RunDevCommand * Made required props non-optional * CLI now points at manual install guides if no Next project detected * Explicitly made supported default to false (it was working but a bit hard to read) * Added links to all github issues for the frameworks coming soon component --------- Co-authored-by: Matt Aitken <matt@mattaitken.com>
75 lines
2.7 KiB
Plaintext
75 lines
2.7 KiB
Plaintext
---
|
|
title: Introduction
|
|
description: "Welcome to the Trigger.dev documentation."
|
|
---
|
|
|
|
Trigger.dev is an open source framework for creating long-running Jobs directly in your app with API Integrations, webhooks, scheduling and delays. You can reliably run Jobs that wouldn't normally work in serverless environments (like Vercel) because of timeouts.
|
|
|
|
You can use [Trigger.dev Cloud](https://cloud.trigger.dev) or [Self-host Trigger.dev](/documentation/guides/self-hosting) on your own infrastructure.
|
|
|
|
<Note>
|
|
Trigger.dev v2 currently only supports serverless. We will be adding [support for long-running
|
|
servers](https://github.com/triggerdotdev/trigger.dev/issues/244) soon.
|
|
</Note>
|
|
|
|
<CardGroup>
|
|
<Card title="Quick start guides" icon="person-running-fast" href="quickstarts/introduction">
|
|
Get started in 5 minutes.
|
|
</Card>
|
|
<Card title="Video walkthrough" icon="video" href="/documentation/guides/video-walkthrough">
|
|
Go from zero to a working Job in your app in 10 minutes.
|
|
</Card>
|
|
<Card
|
|
title="What is Trigger.dev"
|
|
icon="wand-magic-sparkles"
|
|
href="/documentation/concepts/what-is-triggerdotdev"
|
|
>
|
|
Learn more about how Trigger.dev works and how it can help you.
|
|
</Card>
|
|
<Card title="Integrations" icon="grid-2" href="/integrations">
|
|
Trigger.dev integrates with a wide range of services.
|
|
</Card>
|
|
<Card title="Examples" icon="slot-machine" href="/examples">
|
|
One of the quickest ways to learn how Trigger.dev works is to view some example Jobs.
|
|
</Card>
|
|
<Card title="Manual Setup" icon="book-sparkles" href="guides/manual">
|
|
For complete control, you can manually setup Trigger.dev using this guide.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## Getting help
|
|
|
|
We'd love to hear from you or give you a hand getting started. Here are some ways to get in touch with us. We'd also ❤️ your support.
|
|
|
|
<CardGroup>
|
|
<Card
|
|
title="Join our Discord server"
|
|
icon="discord"
|
|
href="https://discord.gg/kA47vcd8P6"
|
|
color="#5865F2"
|
|
>
|
|
The #help-and-questions channel is a great place to get help with any questions about
|
|
Trigger.dev.
|
|
</Card>
|
|
<Card
|
|
title="Follow us on Twitter"
|
|
icon="twitter"
|
|
href="https://twitter.com/triggerdotdev"
|
|
color="#1DA1F2"
|
|
>
|
|
Follow us on Twitter to get the latest updates and news.
|
|
</Card>
|
|
<Card title="Schedule a call" icon="phone" href="https://cal.com/team/triggerdotdev/support">
|
|
Arrange a call with one of the founders. We can help answer questions, build API Integrations
|
|
for you and give 1-on-1 help building your first Job.
|
|
</Card>
|
|
<Card
|
|
title="Give us a star on GitHub"
|
|
icon="star"
|
|
href="https://github.com/triggerdotdev/trigger.dev"
|
|
color="#fbbf24"
|
|
>
|
|
Check us out at triggerdotdev/trigger.dev
|
|
</Card>
|
|
</CardGroup>
|