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>
71 lines
3.1 KiB
Plaintext
71 lines
3.1 KiB
Plaintext
---
|
||
title: "FAQ"
|
||
description: "This section is aimed at collecting common questions from users to provide documented answers."
|
||
---
|
||
|
||
<Accordion title="Can I self-host Trigger.dev?">
|
||
Yes, view our [self-hosting guide](/documentation/guides/self-hosting).
|
||
</Accordion>
|
||
|
||
<Accordion title="Does my data get sent to your servers?">
|
||
Only what you choose to send. The main body of your Job code runs on your infrastructure. For
|
||
example when you do a database query, that never touches us. We receive data that triggers the
|
||
start of a Job, any data you pass to one of our API Integrations, and any data you choose to log
|
||
using our logging function. We store this to display on the Runs page of your dashboard.
|
||
</Accordion>
|
||
|
||
<Accordion title="What frameworks does Trigger.dev support?">
|
||
You can use Trigger.dev with a variety of frameworks. You can check out [the full list
|
||
here](/documentation/quickstarts/introduction).
|
||
</Accordion>
|
||
|
||
<Accordion title="Can I run Trigger.dev locally?">
|
||
Yes. Jobs are created in your code locally.
|
||
</Accordion>
|
||
|
||
<Accordion title="Can I build complex Jobs?">
|
||
Yes. There’s no limit to the complexity of Jobs you can create. Jobs are created in code so you
|
||
can write conditional, looping, branching or time delayed logic.
|
||
</Accordion>
|
||
|
||
<Accordion title="What is a 'Run'?">
|
||
A run is a single execution of a Job. This can be in either development, staging or production.
|
||
[View full details](/documentation/concepts/runs).
|
||
</Accordion>
|
||
|
||
<Accordion title="Can I use version control or roll-backs?">
|
||
Yes. You create Jobs directly in your own code so it’s version controlled with everything else.
|
||
</Accordion>
|
||
|
||
<Accordion title="How long does it take to code up a Job?">
|
||
A simple Job doing a couple of API calls from different services will take about 5 minutes to
|
||
create.
|
||
</Accordion>
|
||
|
||
<Accordion title="Do you have all the Integrations I need?">
|
||
View [our Integrations page](/integrations) to see the Integrations we currently support. If we
|
||
don't have an Integration you need, you can request it or create it yourself.
|
||
</Accordion>
|
||
|
||
<Accordion title="Is Trigger.dev open source?">
|
||
Yes, Trigger.dev is open source. We are strong supporters of open source software, and our first
|
||
product, [jsonhero.io](https://jsonhero.io), has a thriving open source community. Trigger.dev
|
||
follows in that tradition.
|
||
</Accordion>
|
||
|
||
<Accordion title="Is Trigger.dev a no/low-code tool like Zapier?">
|
||
No. Trigger.dev is designed for developers who want to create Jobs directly in code, without using
|
||
a UI builder like Zapier. This allows developers to stay in their familiar development environment
|
||
and customise their Jobs with code.
|
||
</Accordion>
|
||
|
||
<Accordion title="Can non-coders use this product?">
|
||
Developers will need to create Jobs. However, anyone on the team can monitor running Jobs in the
|
||
Trigger.dev dashboard.
|
||
</Accordion>
|
||
|
||
<Accordion title="My question is not listed here">
|
||
Hop in our [Discord](https://discord.gg/nkqV9xBYWy) and ask any question you have in there! You
|
||
could also open a [GitHub issue](https://github.com/triggerdotdev/trigger.dev/issues/new).
|
||
</Accordion>
|