Problem in setting up locally

[monopoly21]

So when i run yarn dev ,the local project starts on localhost:3000 but when i suppose go to another page suppose the my profile section then the projects loads fir a while and eventually stops running on localhost

Steps which i followed:
1.git clone from my forked repo
2. yarn install
3.cp .env.example .env
4. Added required keys using openssl and database connection string from neon.tech
5.ran prisma migrate
6.ran yarn dev

Please help!!
And also please comment/send the discord
community link as the one on website has expired

[dosubot[bot]]

Hey there, @monopoly21! 👋 I'm here to help you with any bugs, questions, or becoming a contributor while you wait for a human maintainer. If you need assistance, feel free to ask!

I found a similar unsolved discussion that might be relevant to your issue: Prisma problem in local setup ^[1].

Regarding your issue, there are a few things you might want to check:

1. Routing Errors: Cal.com uses Next.js for routing, and issues can arise if there are errors in the routing logic. Ensure that all necessary query parameters are correctly set and that the routing configuration is complete. Missing parameters or undefined routes can cause the application to stop running ^[2][3].

2. Database Connection: Ensure that your DATABASE_URL in the .env file is correctly configured. If you're using Neon.tech, verify that the connection string is accurate and that the database is accessible ^[4].

3. Prisma Migrations: Double-check that the Prisma migrations have been applied correctly. If you encounter issues like "The database schema is not empty," you might need to resolve them by marking migrations as applied ^[5].

These steps should help you troubleshoot the issue. If the problem persists, reviewing the console logs for specific error messages during navigation might provide more insights.

To continue talking to Dosu, mention @dosu.

[dosubot[bot]]

The issue you're experiencing with the application stopping when navigating to another page like "Settings" could be related to several factors:

1. Error Handling on the 'Settings' Page: The 'Settings' page in Cal.com has specific error handling mechanisms. For instance, if there's an error fetching organization data, the user is redirected to another page. Ensure that your environment is correctly set up to handle these scenarios ^[1].

2. State Management and API Requests: Issues with state management or API requests can cause the application to stop. Ensure that all API endpoints are accessible and that there are no network issues affecting data fetching.

3. Console Logs and Error Messages: Check the console logs for any error messages when the application stops. These logs can provide insights into what might be causing the issue, such as network request failures or unhandled exceptions.

4. Environment Variables: Double-check that all necessary environment variables are correctly configured. Missing or incorrect environment variables can lead to unexpected behavior.

5. Dependencies: Ensure that all dependencies are correctly installed and up-to-date. Run yarn install again to verify that there are no missing or outdated packages.

Reviewing these areas should help identify the root cause of the issue. If you have specific error messages from the console logs, they could provide more detailed guidance on resolving the problem.

To continue talking to Dosu, mention @dosu.

[monopoly21]

@dosu could you guide me on understanding the codebase

[dosubot[bot]]

To understand the Cal.com codebase, you can follow these steps:

1. Project Structure: Cal.com is organized as a monorepo using Turborepo. This structure helps manage multiple code projects and share code and resources effectively. Check the turbo.json file to understand the different parts of the project and their dependencies.

2. Explore Key Directories:

   • Packages: Located in the /packages folder, this contains various packages used in the project.
   • Web Components: Found in the /apps/web folder, this contains the pages and components for the web application.
   • API Codebase: Located in the /apps/api folder, this contains the public API-related code.
   • AI Codebase: Found in the /apps/ai folder, this contains the Cal.ai related code.

3. TRPC Usage: The project uses TRPC for end-to-end typesafe procedure calls to Prisma. Look at examples of useQuery and useMutation hooks in the codebase to understand how data fetching and mutations are handled.

4. API Validations: The API uses Zod for validations to ensure type safety and error handling. Explore the validation files in /apps/api/lib/validations to understand how requests are parsed and validated.

5. Development Environment: Set up your development environment by following the prerequisites and setup instructions. This includes installing Node.js, PostgreSQL, and Yarn.

By exploring these areas and understanding the dependencies and structure, you can gain a comprehensive understanding of the codebase ^[1].

To continue talking to Dosu, mention @dosu.

[monopoly21]

@dosu
https://www.loom.com/share/1281def304464e80a8f785f8f97b5ca0?sid=f514b6a7-ac0a-41a8-ab51-157cf5a5bb49
in the above video i had run yarn dev and i logged in with the credentials using email pro@example.com as in the video when i go to settings route (http://localhost:3000/settings/my-account/profile ) the dev server stops .Please help

[dosubot[bot]]

The issue you're experiencing, where the development server stops when navigating to the settings route, could be due to several factors. Here are some steps to help troubleshoot and resolve the problem:

1. Check Console Logs: Review the console logs for any error messages when the server stops. These logs can provide insights into what might be causing the issue, such as network request failures or unhandled exceptions.

2. Network Requests: Ensure that all API endpoints are accessible and that there are no network issues affecting data fetching. The application uses trpc for data fetching and mutations, so any issues with these requests could cause the application to stop.

3. Environment Variables: Double-check that all necessary environment variables are correctly configured in your .env file. Missing or incorrect environment variables can lead to unexpected behavior.

4. Dependencies: Ensure that all dependencies are correctly installed and up-to-date. Run yarn install again to verify that there are no missing or outdated packages.

5. Error Handling on the 'Settings' Page: The 'Settings' page has specific error handling mechanisms. If there's an error fetching data, it could disrupt the application. Make sure your environment is set up to handle these scenarios properly.

6. Network Timeout: The error stack trace you mentioned earlier indicated a FetchError due to a request timeout. Ensure that your network connection is stable and that there are no issues accessing external resources like Google Fonts.

By addressing these areas, you should be able to identify and resolve the issue causing the development server to stop. If you have specific error messages from the console logs, they could provide more detailed guidance on resolving the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}