-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A few issues when running locally #238
Comments
You need to run it with --legacy-peer-deps |
change next:"13.4.9-canary.1" to "next": "13.4.8" for the first error |
Here's the link to the guide to set this up locally: https://vercel.com/guides/nextjs-multi-tenant-application (the guide OP linked is not the right one) Also, good catch about these errors, thank you, will fix them now! |
Update: #247 should fix the first error! |
Hi @steven-tey - I was running through the new platforms guide and wanted to call out that I'm new to using pnpm, for some reason ![]() |
Great catch, thank you @Dannydoesdev! I just updated the guide to stick with |
Glad to help @steven-tey! |
Environment variables aren't configured at that point in the guide. So running |
For those stuck as me running locally this config worked for me
And change L44 on middleware from "localhost:3002" to "localhost:3000" |
@octavioamu With this tweak I was able to get the login page of github but when i click "Login with github"... I get the following error: app.localhost sent an invalid response. Any thoughts? |
this will fix if you set env variable ref: stackoverflow |
@afrozegithub did you used https://github-client-generator.vercel.app/ to generate the github app ? |
app.localhost sent an invalid response. ^^^^ The only sort of error logging I'm able to get might not be helpful and only pops up when in the VSCode terminal -- dev still going -- and in chrome hard refresh throws this in the vscode terminal: On all other fronts it appears this doesn't work. Spun up a clean windows VM (I'm on mac)...pulled repo, supplied env, same outcome. app.localhost sent an invalid response. |
When building locally you need to use Otherwise it will cause an error: ~/github/platforms main !5 ❯ pnpm build
> @ build /Users/nikolai/github/platforms
> prisma generate && prisma db push && next build
Prisma schema loaded from prisma/schema.prisma
✔ Generated Prisma Client (4.16.2 | library) to ./node_modules/.pnpm/@prisma+client@4.16.2_prisma@4.16.2/node_modules/@prisma/client in 81ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database
Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Environment variable not found: POSTGRES_URL_NON_POOLING.
--> schema.prisma:7
|
6 | url = env("POSTGRES_PRISMA_URL") // uses connection pooling
7 | directUrl = env("POSTGRES_URL_NON_POOLING") // uses a direct connection
|
Validation Error Count: 1
[Context: getConfig]
Prisma CLI Version : 4.16.2
ELIFECYCLE Command failed with exit code 1. |
@hegelstad You are correct ✅️. You should use |
This is looking really good! Could you add some clear instructions in the readme for how to get all of this working locally?
Could you add some instructions for how to run this locally? I guess that's what https://vercel.com/guides/nextjs-prisma-postgres is for? Trying to follow along does work! But a few minor notes: Currently seeing this:
Anyway after installing with
--legacy-peer-deps
I see some other issues:Also I think some clarity could be made for
TEAM_ID_VERCEL=
- what if you don't have a team but want to play around with this?After adding that in,
npm run dev
-> navigate tohttp://localhost:3000
but it redirects to:https://vercel.com/blog/platforms-starter-kit
. Realise the correct URL should be:http://app.localhost:3000/login
When things are up and running, I can make posts, but get a 404 when I try to view them, etc. at
http://my-local-test-site-1.localhost:3000/
The text was updated successfully, but these errors were encountered: