This is a T3 Stack project bootstrapped with create-t3-app.
We try to keep this project as simple as possible, so you can start with just the scaffolding we set up for you, and add additional things later when they become necessary.
If you are not familiar with the different technologies used in this project, please refer to the respective docs. If you still are in the wind, please join our Discord and ask for help.
To learn more about the T3 Stack, take a look at the following resources:
- Documentation
- Learn the T3 Stack — Check out these awesome tutorials
You can check out the create-t3-app GitHub repository — your feedback and contributions are welcome!
Follow our deployment guides for Vercel, Netlify and Docker for more information.
some points i want to add to this
pnpm dev
#newstuff
##TODO
- Make it deploy (vercel)
- Scaffold basic ui with mock data
- Tidy up build process
- Set up the database with postgres vercel
- Attach database to ui
- Add Authentication with clerk
- Add image upload
- Error management with sentry
- Routing/image page (parallet route stuff)
- Delete button with server actions
- Analytics (posthog)
- Ratelimiting (upstash)
we will be doing git add -p instead of git add -a, by this we will be effectively be doing mini code reviews for the changes we have made
now come to the mock data, we need images, because this is gallery, but hosting your files directly from public has so much issues, such as bandwidth usage, should be avoid by our best of the abilites so for that we are going to be using upload thing, it does charge for the bandwidth at all
i just added another layout in layout2, so what is the use of this??? -> first layer applies in the outside, the second layer applies in the next layer, and as u keep nexting, these layers keep getting applied
why would u ever want this? like for example in dashboard thing, u may always want to top nav to exist, everywhere u r in the dashboard, so in the dashboard folder we have this root layout that have this top nav, now with this we have slietly different url,
we also a have a side nav and a top nav, this layout is so convinient, and doing this in the old model was so miserable so now it's just build into next now
we don't need those layer2, it was just for explaination, so lets remove it
tidy up the build process steps
-
something little controversial next.config.js const config = { typescript: { ignoreBuildErrors: true, }
eslint: { ignoreDuringBuilds, }, };
export default config;
why do we want to ignoreBuildErrors and ignoreDuringBuilds we can check types, we can check eslints in the github actions in the github actions and not to block our builds, we want all of our things in one place
next things is to turn on the infamous turbo pack next dev --turbo in our package.json file and restart our dev environment this will be so much faster, these few quality of life things
vercel gives one free postgres database per account in free tier but their is one work around this, we can share one postgres database across multiple projects u can use tool like drizzle very specifically for this, this very cool feature is enabled by defualt in t3
go to src/server/db/schema.ts
t3 has a prefix in all the tables, which means when u use any database technologies with drizzle in this case postgres, it will only effect things which start with your project name, like in this case newstuff_, with this we can have multiple different projects sharing the database seperated tables with this prefix name
export const createTable = pgTableCreator((name) => newstuff_${name});
we need to actually make sure all this is in an actual database so we have a command in t3, look for it in package.json db:push : drizzle-kit push:pg
migration sucks they fail to acknowledge alot of things that r necessary for scaling the database and also for using these things with teams we have bunch of git diff to show how these things changed in the order we changed them in but migration don't encapsulate that properly they come from a pre version control era, as such it is recommend to use db:push, their is alot of content of this
we r gonna use db:push
we r gonna update the datbase to match our current schema
pnpm run db:push
if we see how this looks in database
to see the stuff in our database we can
pnpm run db:studio
db:studio will take advantabe of drizzle studio, which is super usefull