A few weeks ago, I started playing with Blazor — just a small side project to explore the framework.
When the app started to look decent (thanks to MudBlazor), I figured:
“Why not put it online?”
That's when I remembered how much I miss the old days of FTP and hitting Refresh.
I didn’t want to set up Docker, Kubernetes, or a full CI/CD pipeline to deploy a simple .NET app.
So I started looking for something lightweight — and that’s when I discovered Fly.io.
It took just a few commands to go from dotnet run to a live URL. No configs, no cloud dashboards, no DevOps drama.
Curious?
I wrote a whole post about the process (and how surprisingly smooth it was) — including:
👉 Read the full article here:
Hosting .NET Apps Without DevOps Drama
More...
When the app started to look decent (thanks to MudBlazor), I figured:
“Why not put it online?”
That's when I remembered how much I miss the old days of FTP and hitting Refresh.
I didn’t want to set up Docker, Kubernetes, or a full CI/CD pipeline to deploy a simple .NET app.
So I started looking for something lightweight — and that’s when I discovered Fly.io.
It took just a few commands to go from dotnet run to a live URL. No configs, no cloud dashboards, no DevOps drama.
Curious?
I wrote a whole post about the process (and how surprisingly smooth it was) — including:
- How to deploy a Blazor or .NET app to Fly.io
- What files get generated automatically
- Why I think we overcomplicate things sometimes
- And how to go from zero to online in 5 minutes
👉 Read the full article here:
Hosting .NET Apps Without DevOps Drama
More...