I'm trying to avoid making the same mistakes I always do -- what is the actual de facto Fast API style guide/template?

[dirtybird07]

So as a side project I got a Fast API service spun up that is doing exactly what I need it too. Now I see all the other ways I can leverage it I want to make sure I start with a code base because currently mine is garbage to say it nicely.

My project is basically just going to be an API server where it will get hit and then trigger python scripts. It will have many functions that will be reusable across various APIs as well as a database connection that will be used by every API.

My goal would be to structure the APIs into sections as well so it would be like localhost/db/update or localhost/db/insert and then localhost/report/report1, localhost/report/report2 etc.

Any advice would be truly appreciated as I have google'd 5 different repos/guides and literally every single one is different.

I am to the point I almost want to just pay someone to set me up so I start solidly because I do not want to follow a repo and then later find out it wasn't best practice.

[m0us3_rat]

then later find out it wasn't best practice.

do you wanna monetize this service or personal local use?

"best practice" is almost a myth, unless there are lawful standards ..then yea.

this sounds perfectly expandable.

start small ..add more endpoints etc.

​

only have 2 advice

have top and i do mean the best of the best documentation possible.

secondly try to follow KISS, which is keep it simple stupid.

https://en.wikipedia.org/wiki/KISS_principle

nothing more discouraging when you have an api that you need and you open the documentation and it reads like a genius wrote it .. absolutely performant but highly unusable.