search

BU-Spark / se-editor-ai

Editor AI
https://se-editor-ai.vercel.app
GNU General Public License v3.0
0 stars 1 forks source link

Request for Spark! Tech Resources for editorai #5

Open JslYoon opened 4 months ago

JslYoon commented 4 months ago

Junsun Yoon (lyoon02@bu.edu) Benjamin Gardiner (bengard@bu.edu) Mary Ann Nguyen (nhnguyen@bu.edu) Tia Hannah (thannah@bu.edu)

Google Firebase - frontend web hosting, data store Google Cloud Platform - backend (api) hosting

IanSaucy commented 4 months ago

Hey, what do you need GCP for? What do you plan to host there?

JslYoon commented 4 months ago

We will be hosting our backend (Flask) on GCP

IanSaucy commented 4 months ago

Okay, two things.

I would highly encourage you to use FastAPI instead.

  1. We can get you setup with a project on railway for hosting the API. It is our preference for deployments(it's also easier to work with)
JslYoon commented 4 months ago

Ok that would be nice, we only said GCP because that was listed on the website https://buspark.io/documentation/compute-resources/request-resources we can use railway

langdon commented 4 months ago

Ok, I am now confused. When we talked in the meeting the request was for user auth and document storage. You were considering mongodb for this and I suggested firebase as an alternative.

IanSaucy commented 4 months ago

Whatever is happening, @mannyakosah can you handle this ticket? Probably hold until what stuff is needed is fleshed.

IF a backend is needed I would do FastAPI on Railway. But if one can get away with serverless functions then pure firebase would be good. Firebase supports both Python and JS/TS for functions now.

JslYoon commented 4 months ago

Yes, we need Firebase for frontend deployment & data storage. @langdon suggested that we would need smth to deploy the backend, so I put GCP as written on the website. But if you say FastAPI on Railway is better, we can do that instead.

langdon commented 4 months ago

OK, i think we are having some challenges on "naming".

Web Pages: What do you plan to use for this? a static site generator (a la Jekyll) or something like react.js/next.js? API Server: FastAPI on Railway sounds like the right answer User Auth: Google Firebase Document Storage: Google Firebase Other Data Storage: ?? Do you need more data than user auth and document storage (I am thinking "no" but not sure) Anything I missed: ??

The problem is "backend" and "frontend" do not have clear definitions anymore. I would consider your usage of Firebase "backend" and the API server as "backend" or "middleware." Web is usually "frontend" but user auth is kind of a mix of both.

JslYoon commented 4 months ago

Ok, so to recap:

Our structure will go as next.js - Flask - Firebase

We need Firebase to host our next.js app and deal with data store & user auth.

The reason I mentioned GCP was because we wanted to host Flask (API server) as it was the recommended stack on the spark website. However, if FastAPI on Railway is better, we can use that to host our Flask server instead.

I think there was a misunderstanding, thank you!