Skip to content
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

Open
multiverseweb opened this issue Jan 13, 2025 · 11 comments · May be fixed by #386
Open

[WEBSITE] Create backend to store feedbacks #374

multiverseweb opened this issue Jan 13, 2025 · 11 comments · May be fixed by #386

Comments

@multiverseweb
Copy link
Owner

Store data from user feedback form into database.
Screenshot 2025-01-14 023406

Get involved in the comments to discuss the backend technology and database to be used.

@github-actions github-actions bot added the Review Queued Waiting for the Dataverse's Maintainer to review this issue. label Jan 13, 2025
@multiverseweb multiverseweb removed the Review Queued Waiting for the Dataverse's Maintainer to review this issue. label Jan 13, 2025
@Rucha-Ambaliya
Copy link
Contributor

Rucha-Ambaliya commented Jan 14, 2025

@Tejas-Gupta-7 Can you please give me more information on this? Like how should it be stored and used?

@amin-xiv
Copy link
Contributor

so I'm thinking of using prisma + supabase, because they are so easy to get them up and running

@Rucha-Ambaliya
Copy link
Contributor

@amin-xiv Apologies for the confusion, but may I know if you are a contributor or a mentor?

@amin-xiv
Copy link
Contributor

amin-xiv commented Jan 14, 2025

@amin-xiv I'm a contributor

@amin-xiv
Copy link
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.

@multiverseweb
Copy link
Owner Author

multiverseweb commented Jan 15, 2025

@Rucha-Ambaliya @amin-xiv initially I thought that we can use the django framework as it is easy to implement. But it is not efficient for fast transactions and therefore is not scalable.

Using supabase and prisma will also limit our data storage to 500MB (free plan).

I think using Node.js and MongoDB can be a good option. What do you think?

Let me know if you are familiar with these technologies or have a better option.

PS:
We have to store the feedback data in any format (json/CSV/relational form) and display it on the Reviews Page.

@Rucha-Ambaliya
Copy link
Contributor

@Tejas-Gupta-7 I think FastAPI will be a good option considering the entire project is built on Python, and it actually supports fast transactions, making it highly scalable.

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 FastAPI will be the most suitable for it.

@multiverseweb
Copy link
Owner Author

Okay @Rucha-Ambaliya, we can go with FastAPI.
Good luck!

@Rucha-Ambaliya
Copy link
Contributor

Okay.
Thanks you @Tejas-Gupta-7!

@Rucha-Ambaliya
Copy link
Contributor

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!

@multiverseweb
Copy link
Owner Author

Sure @Rucha-Ambaliya, you can send a PR for the tasks you have completed till now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants