manage-fastapi
manage-fastapi copied to clipboard
[WIP] Structural Refactoring - Do not merge yet!
I'm in the process of upgrading the manage-fastapi
library. The main priority of the changes is to provide a more complete structure for setting up projects. Some examples include:
- A flat project structure for better navigation.
- Include routes for things like auth(N & Z).
- Tests both for the produced projects and
manage-fastapi
itself. - Stronger configuration capabilities (multiple possible dev environments with the same code).
- Secrets management.
- Easy deployment methods (possibly to Kubernetes)
- More development feedback loops (with tests and DevOps tools).
- Integrated cli tools (with
typer
)
The reason for attempting to add these to the project is to reduce overall duplication. Ultimately, these pieces of code have been rewritten multiple times over through my projects. Instead of continuing to rewrite them, I'd like to write them once and never again.
This is the first of many commits for this.
What would be the idea here?