cms
cms copied to clipboard
code100x
Add purchases, payment information
Right now, a lot of the backend (user auth and course purchases) is deligated to appx We want to create a strategy where courses can be bought in house This will require some schema design so if you're thiniking of working on this please post the schema and approach first
@hkirat, after some investigation, I've discovered that we're currently relying on an external API/service to verify whether a user has purchased the course or not. Your suggestion seems to be to bring this process in-house. Here's a rough approach I've outlined based on your statement. Please review and let me know if any adjustments are needed.
1). We will add one more field in course model which will tell us ,
model Course {
// Existing fields...
inhouse : Boolean (we can use enum over here also , as u taught us ..)
// Other fields...
}
2). We will add a purchase model in the db .. something like this ..
model Purchase {
id Int @id @default(autoincrement())
userId String
user User @relation(fields: [userId], references: [id])
courseId Int
course Course @relation(fields: [courseId], references: [id])
purchasedAt DateTime @default(now())
.... (few more fields)
}
3). Wee will modify the name of UserPurchase model to something like ... UserCourses model which looks like this..
model UserCourses {
user User @relation(fields: [userId], references: [id])
userId String
course Course @relation(fields: [courseId], references: [id])
courseId Int
assignedAt DateTime @default(now())
@@id([userId, courseId])
}
4). We will add a payment model as well which looks something like this .
model Payment {
id Int @id @default(autoincrement())
purchaseId Int
purchase Purchase @relation(fields: [purchaseId], references: [id]) (this is the new model above we have created .)
method String // e.g., "Credit Card", "PayPal"
amount Float
transactionId String
}
5).. I think by doing above these things we have to 100% change some of our application logic as well
6). Lot of Testing and on spot changes will be required ..
7). I am a beginner in this thing , so please consider that fact as well
@hkirat please have a look
@hkirat, my approach would be. Assuming we are using razorpay for handeling course purchases. The following model should be fine:
model User {
id String @id @default(cuid())
name String?
email String? @unique
phoneNumber Int @unique // Added
transactions Transaction[] // Added
}
// Added a model for razorpay
model Transaction {
id String @id @default(cuid())
razorpay_paymet_id String @unique
razorpay_order_id String @unique
razorpay_signature String
purchasedAt DateTime @default(now())
purchasedCourse Course @relation(fields: [purchasedCourseId], references: [id])
purchasedCourseId Int
purchasedBy User @relation(fields: [purchasedById], references: [id])
purchasedById String
}
model Course {
id Int @id @default(autoincrement())
appxCourseId Int
discordRoleId String
title String
imageUrl String
description String
openToEveryone Boolean @default(false)
slug String
content CourseContent[]
purchasedBy UserPurchases[]
transactions Transaction[] // Added
}
// Rest of the models
Endpoints:
/singup for creating new accounts. Need to validate email or phonenumber to prevent spam
/courses/:courseId/purchase for handling payments with razor pay
Still there are a lot of things that are ambiguous
- Are we planning to handle CMS ourself?
- How can we migrate all prior users from appx to this solution? Would love to clarify those and work on it
Happy to integrate if you think this approach sounds fine 🙇
@hkirat, my approach would be. Assuming we are using razorpay for handeling course purchases. The following model should be fine:
model User { id String @id @default(cuid()) name String? email String? @unique phoneNumber Int @unique // Added transactions Transaction[] // Added } // Added a model for razorpay model Transaction { id String @id @default(cuid()) razorpay_paymet_id String @unique razorpay_order_id String @unique razorpay_signature String purchasedAt DateTime @default(now()) purchasedCourse Course @relation(fields: [purchasedCourseId], references: [id]) purchasedCourseId Int purchasedBy User @relation(fields: [purchasedById], references: [id]) purchasedById String } model Course { id Int @id @default(autoincrement()) appxCourseId Int discordRoleId String title String imageUrl String description String openToEveryone Boolean @default(false) slug String content CourseContent[] purchasedBy UserPurchases[] transactions Transaction[] // Added } // Rest of the modelsEndpoints:
/singupfor creating new accounts. Need to validate email or phonenumber to prevent spam/courses/:courseId/purchasefor handling payments with razor payStill there are a lot of things that are ambiguous
- Are we planning to handle CMS ourself?
- How can we migrate all prior users from appx to this solution? Would love to clarify those and work on it
Happy to integrate if you think this approach sounds fine 🙇
How about removing transactions field from user and Course table and putting it in UserPurchases. It is refrenced in both user and course table and putting transaction in the userPurchase which is the link between user and course is more appropriate.
@hkirat, yes absolutely can't wait to do it.
Could you please assign this to me?
// Define the User model model User { id String @id @default(cuid()) name String? email String @unique phoneNumber Int @unique transactions Transaction[] // User has many transactions }
// Define the Transaction model model Transaction { id String @id @default(cuid()) razorpay_payment_id String @unique razorpay_order_id String @unique razorpay_signature String purchasedAt DateTime @default(now())
purchasedCourse Course @relation(fields: [purchasedCourseId], references: [id]) purchasedCourseId Int purchasedBy User @relation(fields: [purchasedById], references: [id]) purchasedById String }
// Define the Course model model Course { id Int @id @default(autoincrement()) appxCourseId Int discordRoleId String title String imageUrl String description String openToEveryone Boolean @default(false) slug String content CourseContent[] purchasedBy UserPurchases[] transactions Transaction[] // Course has many transactions }
// Define the CourseContent model model CourseContent { id Int @id @default(autoincrement()) courseId Int content String // Define any other fields related to course content }
// Define the UserPurchases model model UserPurchases { id Int @id @default(autoincrement()) userId String courseId Int purchaseDate DateTime @default(now()) amount Float // Define any other fields related to user purchases }
