I’m excited to share my new open-source project: Fastapi-Template
It’s designed to give you a solid starting point for building backend APIs with FastAPI while incorporating best practices so you can focus on business logic instead of infrastructure. You can check the docs folder for a walkthrough of the architecture and code.
Highlights
- Token authentication using JWT with secure password hashing
- Async SQLAlchemy v2 integration with PostgreSQL
- Database migrations using Alembic
- Organized folder structure with clear separation for routes, schemas, services, and repositories
- Structured logging with Loguru
- Ready-to-use .env configuration and environment manage…
I’m excited to share my new open-source project: Fastapi-Template
It’s designed to give you a solid starting point for building backend APIs with FastAPI while incorporating best practices so you can focus on business logic instead of infrastructure. You can check the docs folder for a walkthrough of the architecture and code.
Highlights
- Token authentication using JWT with secure password hashing
- Async SQLAlchemy v2 integration with PostgreSQL
- Database migrations using Alembic
- Organized folder structure with clear separation for routes, schemas, services, and repositories
- Structured logging with Loguru
- Ready-to-use .env configuration and environment management -Pre-commit hooks and code formatting
- Example cloud storage integration using Backblaze B2
Why did I build it?
Having worked on numerous APIs for backend systems, i wanted to remove the time that is consumed to create the folder structure every time i start a project for FastAPI.
Note:
Feel free to edit it to match your tone, add any screenshots or code snippets you want, and adjust the bullet points to emphasise what you care about most.
If you think something is missing, needs refactoring, or could be better structured, I’d love to hear your thoughts in a comment below or open a PR on Github.