Primrose backend project
18 July 2026
Category: Portfolio
Hallo everyone,
this was big. I wanted to create a complete backend project, with all the bells and whistles. So I created PrimroseBackend.
It’s a complete backend project, with user management, authentication, authorization, and a simple game (tic-tac-toe) to demonstrate the functionality.
The project is built with ASP. NET as a backend, React as a frontend, MSSQL, Flutter & Dart for web-view-based mini application and Caddy.
It’s a complete production-ready project, with all the necessary features to get started with a real-world application.
To my knowledge, it conforms to the best practices and is a good starting point for any backend project. Including
sensitive data protection, logging, and error handling.
What constitutes this backend project:
- ASP.NET 10 backend with Entity Framework Core
- React 19.2. frontend (different repository)
- MSSQL database
- Flutter & Dart web-view-based mini application (different repository)
- Docker used for containerization and deployment
- Caddy used as a reverse proxy
- JWT authentication and authorization
- Whole thing is hosted on my server on Hetzner Cloud
- Cloudflare used for hosting and DNS management
But what can all this actually do and what’s its purpose?
Well, it all has begun when I wanted to use WebView in an app. I wanted to test it hands-on on something practical. And since
I’m a bit tired of all those services with special rules and tons of features and limitations and price-tags,
I wanted to develop my backend project, which would be a simple service for my own use. I wanted to have a simple user management system,
with authentication and authorization. Data and database storage and have it all under control. To understand how it all works
together and why things are done as they are done in the production world.
And I did. Made research, burned once on trying to use ClouFlare tunel as a reverse proxy, which turned up to be not practical
and cumbersome, so I switched to Caddy, which worked just great.
In the end I have a administration frontend where I can manage users for this backend service and also manage what pages are displayed in
a web-view application (as a demostrative example).
Of course, this can be extended as a backend service for any number of webpages and mobile applications.
The thing is I can use this same frontend for many more pages or aps, because login is filtering what the user can see and the user can see only what is allowed for them.
I can use this very same infrastructure for any future project of mine or for my clients.
This makes me happy and I’m looking forward to use this thing in the future :)
Keep coding!
Petr
You won’t be able to use it, because I won’t publish any login credentials, but you know, just to see that it works :D Health Check is a life thing.
