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
chore: init new example #5595
base: next
Are you sure you want to change the base?
chore: init new example #5595
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
Diagnostics ComparisonNumbers
Timings and averages
unstable timingsUnstable
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a vercel deployment with a db + repo in the trpc org + subtree?
(Oooor just add drizzle to the existing example)
@@ -0,0 +1 @@ | |||
AUTH_SECRET=FlIbvvIt9KQXVBcg0wKpcrHMwGA5RNxpxn826LdbBF8= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't store stuff like this in git
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha just wanted the example to start right up 😅😅 not like that auth token does anythign secret
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, but if people clone the project they will get the a bad setup, .env
should be in .gitignore
:)
form={form} | ||
handleSubmit={async (values) => { | ||
const promise = addPost(values); | ||
return toast.promise(promise, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't this toast twice on errors? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should the db really be checked in? shouldn't that be lazily created with migrations or smth?
can we do something that works to deploy on vercel? like sqlite locally and pg on vercel?
inits a new next app dir example with just the new caller stuff.
really simple with drizzle sqlite and next auth credentials provider:
CleanShot.2024-03-28.at.00.47.46.mp4