-
Notifications
You must be signed in to change notification settings - Fork 112
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
[WEBSITE]
Create backend to store feedbacks
#374
Comments
@Tejas-Gupta-7 Can you please give me more information on this? Like how should it be stored and used? |
so I'm thinking of using prisma + supabase, because they are so easy to get them up and running |
@amin-xiv Apologies for the confusion, but may I know if you are a contributor or a mentor? |
@amin-xiv I'm a contributor |
@multiverseweb can I get assigned? I'll do it with prisma and supabase, it's really simple and I have prior experience with it. |
@Rucha-Ambaliya @amin-xiv initially I thought that we can use the Using I think using Let me know if you are familiar with these technologies or have a better option. PS: |
@Tejas-Gupta-7 I think I have worked with all four technologies—MongoDB, FastAPI, Node.js, and Django—so whatever you think is best, I'll work with that. Personally, I believe |
Okay @Rucha-Ambaliya, we can go with FastAPI. |
Okay. |
I’ve set up FastAPI and MongoDB, restructured the folders accordingly and have also updated documentation. Is it fine if I raise a separate PR for this setup before working on the models and fetching data from reviews? This will help me keep track of the changes I’ve made and ensure the setup is clean and isolated from the model work. By splitting the PR, I aim to ensure that the setup is well-organized and easier to troubleshoot later, which will make the integration with models and reviews smoother. Let me know if that works for you! |
Sure @Rucha-Ambaliya, you can send a PR for the tasks you have completed till now. |
Store data from user feedback form into database.
Get involved in the comments to discuss the backend technology and database to be used.
The text was updated successfully, but these errors were encountered: