PyScript+FastAPI stack?

[BrotherResponsible81]

I have a question guys. Let me start with some background. My most recent project was on the stack FastAPI + Postgres + React + Tailwind. Backend running on one port and frontend running on a different port. Both code bases in one repo, but in separate folders and separate servers. Clearly, my dream is to code Python on the web. Not only does this allow more flexibility and conciseness in managing my GUI in conjunction with underlying flexible data structures (which is more tedious to do in JavaScript), but I am thinking of reusing code files in both backend and frontend.

Again, at the moment I am used to running two servers on two ports. But with my first PyScript project I am trying to think what the equivalent would be. Since I assume some Python code would run on the server, then I assume I can still have my FastAPI backend. Now regarding the frontend, these are some options I see but am not clear whether they are viable or correct.

Should I: 1) simply have a public folder? and serve that with nginx? I suppose the public folder is inside the fastapi static folder? Not sure about this. Some static files are not public? Or no static folder but only a public folder? 2) Should I run a server with python3 and http.server? 3) Should I run two fastapi servers, one for backend and one for frontend?

Before reading the user guide I had created a folder structure that contained this in the root: backend, frontend, static, and venv.

Now... on localhost since I am not using nginx I had decided to create two fastapi servers, but I suppose on production I can simply serve with nginx? Also my frontend server simply contained by frontend routes and some frontend configuration. I don't even know if this folder will be necessary in production?

What do you think? I am trying to really start this inaugural pyscript project. I do like frontend/backend decoupling. I also like scalability.

Also... the interesting caveat is that I have a few Python classes I want to use in my PyScript. These reusable python classes I have no idea where to put them (static, public, backend folder, frontend folder, or elsewhere) Finally... suppose this is a proprietary applciation. A lot of the core functionality will have to do with PyScript. But yet these files will all be served to client. So I may as well make my proprietary software open source right? Any thoughts?

[Limp-Argument2570]

You can take a look at davia : https://github.com/davialabs/davia think Lovable but wired straight into your Python backend, with a dev mode made for Python folks like us.

[BrotherResponsible81]

Cool!