[TRI-857] Record the setup experience and provide feedback

[matt-aitken]

We are looking for 10 people to record themselves doing the setup experience of the product.

For each completed recording, we'll be giving a $100 tip using Algora.

Purpose

We are trying to make the initial experience better. That includes the CLI, in-app onboarding, and the quick start docs.

Requirements

• You haven't used the product before.
• You do a continuous screen recording with your microphone turned on, ideally camera too but that's optional.
• Say aloud what you're thinking.

What should go in the video

Try and do the following:

1. Create a Trigger.dev account: https://cloud.trigger.dev
   1. Use the invite code: continuous-delivery-862
2. Go through the process of getting setup. Behave how you normally would trying to get it working.
3. Get the example Job running

If you get stuck or experience a bug, that's very useful. Don't cut this out of the video. Please share using the method below.

Submission

Do not create a Pull Request.

1. Add a comment to this issue with the video attached.
2. (Optional but appreciated) Add any comments you have about how things could be better.
3. We will send you the £100 tip using Algora

_{From SyncLinear.com | TRI-857}

[matt-aitken]

/bounty $100

[algora-pbc]

💎 $100 bounty created by matt-aitken
👉 To claim this bounty, follow the submission guidelines above
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to triggerdotdev/trigger.dev!

[ericallam]

There's also no need to create an attempt, as this is an open-ended bounty and will no be awarded through the normal bounty procedure 👍

[zodman]

First one! https://drive.google.com/file/d/1N4x7cSKnAn4SY4fIST3izCwZzxWuuF5u/view?usp=drive_link

other feedback is on the intervalTrigger I want to see when will be the next operation at least at the console.

the next execution will be at XX:XX XXX

Dont put Coming soon and #250

And like a tool for developers to have to enhance the pricing for a solo developer... I will prefer to create my custom api/triggers/task and execute by uptimerobot in a webhook every 5min.

And uptimerobot will reportme the status if it was success for better price. (your mpv was fully replaced by a custom implementation+uptimerobot ).

[ericallam]

/tip $100 @zodman

[algora-pbc]

🎉🎈 @zodman has been awarded $100! 🎈🎊

[rishi-raj-jain]

I'm on it right now.

[rishi-raj-jain]

Mine!

• Part 1: https://drive.google.com/file/d/1RQ_AFtDQUrogtC7Hf5Ebg6ghZuCdB_Lb/view?usp=drive_link
• Part 2: https://drive.google.com/file/d/1eu_5xOmfZTTNP2VdP013TLb3Ypr5sPfw/view?usp=drive_link
  (had to stop in between for a minute or two hence the two parts)

Thoughts:

1. Make the homepage super crisp:
   -- Cron's have a lot of configuration to see on the first view, just remove everything and put the required ones so that you can stress what's the benefit with minimal configuration
   -- Similar feedback for events and webhooks

2. Event & Webhook both need to be educated to the customer:

• A webhook flow would be like say I'm going to Storyblok and adding an endpoint to POST to
  -- In this case, how does the "webhook" case separate from "API endpoint"?

• In Event, What exactly is event? Like an event could be Storyblok hitting a POST endpoint because I made some changes in the CMS. What differentiates an event from webhook?

3. Improve the Next integration: As you could see in the video, it failed to detect my Next.js app! while it worked fine with the new app that I spun up next.

4. Highlight the difference between dev and production mode clearly: While I was clearly able to run the dev mode and test a job, I still searched docs, looked here and there to find that it was already on the dashboard suggesting me to use the Web console for the same. This needs a major improvement via CLI/NPM Package using the console to display the message and the mode the user is in.

[Anshul1811]

I also tried to run this and here is my video link .
https://drive.google.com/drive/folders/1G93DFR1IX3c5a1bJ9R-y4jilEGbzvxMv?usp=sharing
(There are 2 videos because in the 1st one my VS code setup is not visible so I tried to show it in the second part)

FEEDBACK:---
1.The docs and the steps mentioned are very helpful and useful.Whenever I got stuck there are steps available to guide through thats a nice thing to have.
2.I am able to successfully setup the job part in just span of few minutes despite being a begineer.So,I can say anyone can setup this easily it is purely begineer friendly.
3.So for me the overall experience was extremely good and I will definitely look forward to use these APIs in my future projects.

[RamK777-stack]

Hi, I have tried Trigger.dev for the first time today. here I am sharing my experiences.

https://drive.google.com/drive/folders/18sRiRdjguhTPQZt-de6nDE9UsNtjEyUn I uploaded as 3 parts because I am facing issues with node.js and next project in my machine.

Initially, during the onboarding process, I am facing some design issues and validation issues. I think it's due to my screen size (13 inches). mentioned those in the above video.

other than that overall experience is good, since I am new to this. I don't understand what this tool is for and what triggers are, jobs, etc.

Also, we can better improve this part in the readme section -> About Trigger.dev
Create long-running jobs directly in your codebase with features like API integrations, webhooks, scheduling and delays.

with the existing problem and how trigger.dev solving that problem, because as a new commer, not able to understand the need for this tool clearly.

Currently, I am reading the documentation, and I will definitely try this in my current project.

Thanks.

[kaf-lamed-beyt]

I tried creating a Job by following the exact steps illustrated in the docs. I noticed some issues with the content in the doc that were not correlating.

Like the one in the image below. It says I'll find the example job in the API routes folder, but it wasn't there, rather It was in the jobs folder inside src

I also included some findings i made in the video.

Here's the link to the test with the /pages dir: video

I'm carrying out another test with the appDir, when I'm done, I'll update it this comment with the link.

Edit: creating a test job with the appDir worked. Here's the link to the video

[yashug]

Hi, I completed a fresh setup of trigger.dev. The concept is cool, and I've provided a video walkthrough of the setup: Link to Video

Feedback:
During the setup, I encountered an issue while running the CLI init command. The problem was that the next app I created wasn't initialized with git using the git init command. It took me some time to debug this as it wasn't mentioned in the documentation as a required step for the next project. I was able to resolve it by checking the CLI section and focusing on the terminal animation, which said, "You have uncommitted git changes, you may want to commit them before continuing." This made me realize that git init for the next project is mandatory before running cli init.

Other points:
The rest of the process was smooth, and I was able to run the example trigger successfully.
Additionally, the guide should mention the creation of the "jobs" folder inside the app or pages directory, as it's not currently mentioned in the quick start guides. However, it is mentioned on the cloud dashboard.
Overall, I enjoyed the experience, and the product has great potential!

[jobenjada]

Love the idea of this, will steal it for Formbricks at some point 😄

[IMPranshu]

My recording is on the way. Thanks

[Roshan-Horo]

Hello all, I completed the setup with next.js ( quick start guide ), it was smooth setup because of the really good docs.

Raw Video of the setup from start to finish ( 40 min ) : Video Link

Docs is really to the point, short and clear for most of the developers and beginner can also run it's first job.

I'm happy with the current state of the docs, but we can improve even better.

Feedback :

• We can have different section for the init command - Trigger.dev Cloud and Self-hosting , for the Trigger.dev cloud , we got init command from dashboard which can add api key directly to .env file, and for the self-host we have to add it (which can be a small note )

[samejr]

/tip $100 @rishi-raj-jain

[algora-pbc]

🎉🎈 @rishi-raj-jain has been awarded $100! 🎈🎊

[samejr]

/tip $100 @Anshul1811

[algora-pbc]

🎉🎈 @Anshul1811 has been awarded $100! 🎈🎊

[samejr]

/tip $100 @RamK777-stack

[algora-pbc]

🎉🎈 @RamK777-stack has been awarded $100! 🎈🎊

[IMPranshu]

My setup video link on youtube https://youtu.be/N0fhfBbXInk

Some issues that I faced during the setup were as follows:-
1- I felt lost while going through the initial setup. So proper directions for the things that can be done afterward should be prominently displayed.
2- I encountered a bug in the following

he docs and then modified the code I was up and running(as displayed in my setup video as well)

3 - Also I belive the project has to be a git project then only we can install the trigger.dev which is not mentioned.

4- Throws not a Next.js project error in older next js versions

[samejr]

Amazing! Looking forward to watching it 👍

[IMPranshu]

I have updated the video link. It got uploaded in youtube when re-uploaded. https://youtu.be/N0fhfBbXInk
Video is still processing, I will update you once 100% processed

[IMPranshu]

Hey @samejr SD quality is up. 4K processing 120 mins remaining. Apologies!!!

[samejr]

Nice one, thanks @IMPranshu – i've got the 360p quality so far so will wait for the 4K 😃

[IMPranshu]

Yup. Will update you once 4k is done.

[IMPranshu]

4k upload done. Please do give feedback @samejr

[samejr]

Hi @IMPranshu just checked it out and it's great! Thanks so much.

[samejr]

/tip $100 @IMPranshu

[algora-pbc]

🎉🎈 @IMPranshu has been awarded $100! 🎈🎊

[pkdjne]

I have tried the instructions.
Some feedback : - I was using an older next js and the error thrown by the app CLI was I was not using Next.js app which i think is misleading instead it should tell that I am using an older version on next.js, that will help.

My video link

[shubhi2000]

I am on it right now. I believe I would be the 10th!

[abhishekmishragithub]

/attempt #249

@matt-aitken First of all the project is really good, the idea of having a job framework for next js app is neat. (I come from a Python background heavily and have used celery for most of my background job)

Regarding bounty :

I got the following error at the first step itself i.e. Initializing the trigger dev in a project with the following command:

npx @trigger.dev/cli@latest init -k tr_dev_ixxxxxx -t https://cloud.trigger.dev

• Error: FetchError: request to https://api.trigger.dev/api/v1/whoami failed, reason: Socket connection timeout

• Screenshot:

• Note: The Next.js app is the sample app created using - npx create-next-app@latest. You can ignore the last few min of the video as i was looking for the docs.
• Video: https://youtu.be/vcOoIza7xWA. Please watch at 1.25x - 1.5x speed 😄

[shubhi2000]

I am on it right now. I believe I would be the 10th!

@samejr @ericallam I had added my work above. Please review and provide provide your feedback.

[samejr]

/tip $100 @pkdjne

[algora-pbc]

🎉🎈 @pkdjne has been awarded $100! 🎈🎊

[samejr]

/tip $100 @shubhi2000

[algora-pbc]

🎉🎈 @shubhi2000 has been awarded $100! 🎈🎊

[samejr]

/tip $100 @abhishekmishragithub

[algora-pbc]

🎉🎈 @abhishekmishragithub has been awarded $100! 🎈🎊

[samejr]

Thanks to everyone who contributed to this issue – your feedback has been really helpful 🙏

[abhishekmishragithub]

@matt-aitken or @samejr can you or someone help me with digging more with the error? or the cloud is still experimental? I wanted to explore more about how the jobs are done.

[samejr]

Hey @abhishekmishragithub im still going through some other videos but will get back to you when i've checked yours out properly.

[abhishekmishragithub]

Hey @abhishekmishragithub im still going through some other videos but will get back to you when i've checked yours out properly.

Sure! Thanks.

[IMPranshu]

Hey @abhishekmishragithub which node version are you running?

[abhishekmishragithub]

Hey @abhishekmishragithub which node version are you running?

v20.0.0

[IMPranshu]

Ok. One thing I have found is this error occurs when the CLI is not able to make a remote connection, which can be solved by using a different api key but in this case you might have to signup with a different account altogether.
Can you try doing that once and see if it resolves the error?

[abhishekmishragithub]

Ok. One thing I have found is this error occurs when the CLI is not able to make a remote connection, which can be solved by using a different api key but in this case you might have to signup with a different account altogether. Can you try doing that once and see if it resolves the error?

I will use different accounts and test. Will follow the approach mentioned in the docs. Thanks!

[IMPranshu]

Also try upgrading or downgrading node version. I am using v20.3.1 and didn't face this issue but there are reports for other apps getting timeout error for v20.0.0

see this npm/cli#3078