A platform being built in the open — and you can watch it happen.
This site is not a business card. It is the project itself: requirements, architecture, code, server and deployment take shape in public, and have been readable from the first commit.
The idea
Most portfolios show the result. Here the route is on record too: why Next.js and not Astro, why no mediator framework, why database migrations do not run when the application starts. Every one of those decisions is written down — with the alternatives that lost, and the condition under which it should be reconsidered.
That includes the mistakes. I learned that a cancelled check in the deployment pipeline is not a failure — and therefore silently ships nothing — by having it happen to me. It is in the documentation now, together with the fix.
Status
Done
- Requirements and architecture
- Server, containers, reverse proxy, backup
- Browser → frontend → API → database, live
- Delivery: build, tests, images, migration, verification
- German and English
Next
- Project catalogue and content management
- Public project pages
- Observability and metrics
- End-to-end tests
Read on
- RepositoryCode, documentation and history in one place
- Architecturearc42: context, building blocks, runtime, deployment, risks
- DecisionsEvery architecture decision with its rationale and alternatives
- Run it locallyWhat you need to build and run the whole thing yourself
Built with
- C# / .NET
- TypeScript
- Next.js
- PostgreSQL
- Docker
- Traefik
- GitHub Actions
- Linux
About me
From the shop floor through work scheduling into IT. Today an application analyst: I run a manufacturing execution system, turn needs into requirements, test them and put them into production — between the business and the system. I learned to build software alongside my job, and keep it alive in projects like this one.