I have a little python and java (school) experience under my belt, but nothing professional or complete. I am trying to create a small database using MySQL, which I think I already figured out. I am using Python to build functions that let me edit the database and pull information from it. That too I have already figured out how to do. The last problem is creating something for users to interface with so that they too can edit the database.
The db will be on my own server, I think I can run a full python app from the server. But I was thinking of a web browser interface so users can just go to a web page rather than having to run a .exe or whatever.
From reading, I see suggestions of using Flask. Is that generally correct? I'll have my SQL db, python app(s) going back and forth with each other. And then Flask going back and forth between python and HTML/CSS? Really I just need to have access to html forms that send data to a python function that modifies the db. Or is using just a plain python GUI okay? It would certainly cut down on trying to brush up on my html, css, and javascript.
My brain is just kind of overloaded right now and any help would be appreciated.
Due to software being infinitely abstractable, there are a ton of different strategies around how to define layers. Web stuff is already complicated enough, so I don't want to to overload you with all the common software design / architecture strategies, ha.
I think a good starting place for a beginner is to create a simple CRUD app. In a CRUD app with an anemic domain model, stuff that users see in the front end is (relatively) directly retrieved from the database through a "model", usually an ORM like SQLAlchemy or Django's, and entering data from the front end is also pretty directly entered into the models. Any tutorial about Flask + SQLAlchemy or Django will have you define these layers (model, routes, views/templates) following is h CRUD paradigm.
This is a good place to start because there's plenty of context to learn around it already without talking about the other layers that devs sometimes use. The domain will make a lot more sense once you've picked up the following knowledge and that takes time:
It's a lot! But don't get overwhelmed, everybody had to go through this phase where everything is poorly explained and you don't know what to do next. Building a CRUD app and really understanding what every piece is doing will already knock out half of the above.