Login

u/Nk0BaNaNE

r/dotnet r/Supabase r/devtools
▲ 4 r/devtools

Looking for repos that are annoying to get running (I'll write the config)

I've been working on a small tool called QuickRun. You point it at a git repo and it clones it, checks what you need installed, shows you the commands and runs it. It works on most repos without any setup, but it works a lot better when the repo has a small quickrun.yml that says how to start it.

There are about 170 configs in the repo by now, for stuff like Sonarr, Radarr, ComfyUI, FreshRSS, Stirling PDF and so on. Most of them I generated from a container catalog, the rest I wrote by hand. They live in the repo under configs/. Doing that alone doesn't really scale, so I'm asking for help.

If you maintain a project, you could add a quickrun.yml to it. There's a builder in the app that writes and tests it for you. If you want, you can also add the badge to your README so people can start it with one click:

[![QuickRun](https://quickrun.org/badge.svg)](https://quickrun.org/run?repo=owner/repo)

If you don't maintain anything but have a favorite project, a PR with a config for it would be great, either to that project or to configs/ in my repo.

And if that's too much, just drop a repo name in the comments or open an issue. Something you always wanted to try but the setup scared you off. I'll write the config for it.

Repo: https://github.com/fgilde/QuickRun

Docs: https://quickrun.org

reddit.com
u/Nk0BaNaNE — 4 days ago
▲ 5 r/dotnet

AspireUI a little web tool to spin up and test self hosted stacks

I built a little web tool to spin up and test self-hosted stacks on my Proxmox box

So this started as a scratch-my-own-itch thing. I run a Proxmox server at home and I kept wanting to try out different stacks and container setups, but I got a bit frustrated with Umbrel/CasaOS and the like. They're nice if you just want to click-install an app, but the second I wanted to actually change how something was wired up or test my own combination of services, I hit a wall.

So I made AspireUI. It's basically a visual builder where I can throw together containers, wire up dependencies, tweak env/ports, and just hit run to see if it works. I can also import an existing docker-compose or a git repo and mess with it from there, then deploy it properly when I'm happy. For me it's turned into the fastest way to prototype a setup before I commit to it.

It's still rough in places and very much a work in progress, but it's already saved me a ton of time on my own box.

Figured someone else here might get use out of it. Happy to hear what you'd want it to do.

You will find it here https://github.com/fgilde/AspireUI

u/Nk0BaNaNE — 3 months ago
▲ 1 r/dotnet+1 crossposts

Own your Lovable app: generate a .NET Aspire AppHost that runs Supabase + your frontend locally (and deploys to Azure/K8s/Docker)

TL;DR: aspire.love turns your Lovable app into a self-contained .NET Aspire solution. One command runs your whole stack locally — Supabase, edge functions and the Vite frontend — and the same solution deploys to Azure Container Apps, App Service, any Kubernetes cluster or plain Docker. Free, MIT, open source.

Lovable is great for shipping fast, but your project ends up wired to hosted Supabase and a build pipeline you don't really control. I wanted my code to run on my machine and deploy wherever I want — no vendor account required.

So I built aspire.love. Point it at your existing Lovable project and it generates a clean, readable aspire/ folder (a .NET Aspire AppHost) that orchestrates everything:

dotnet tool install -g love.aspire
aspire-love init --path ./my-lovable-app
aspire run

That's it — Postgres, Auth, Storage, Realtime, Studio, your edge functions and the frontend all come up together, with the .NET Aspire dashboard showing live logs and traces.

https://preview.redd.it/ce33gnlqs78h1.png?width=1214&format=png&auto=webp&s=6af2690b7e0f1a1ab2d7c58108d5fe097d5a2262

What you get

  • 🧩 Three modes: Full Local (everything in Docker), Supabase Sync (local stack seeded from your cloud project), or Remote Connect (talk straight to your existing cloud project)
  • ☁️ Deploy anywhere: the generated solution is standard Aspire — azd up to Azure Container Apps, or ship the containers to App Service / Kubernetes / your own Docker hosts
  • 🔐 You own everything: your migrations, edge functions, a seeded admin user, optional Grafana/Tempo/OpenTelemetry observability, optional persistent storage for the cloud
  • 🤖 Lovable AI keeps working locally (just bring your LOVABLE_API_KEY)
  • 🖥️ CLI + desktop app: prefer a UI? The Fluent aspire.love Studio walks you through every option with live validation and a live AppHost.cs preview — and auto-updates itself

https://preview.redd.it/sx2awylrs78h1.png?width=1806&format=png&auto=webp&s=bb27b75206a1b4d68e506b925795c7e31d78d841

Under the hood it's powered by the open-source Nextended.Aspire.Hosting.Supabase integration, which makes the whole Supabase stack a first-class Aspire citizen.

Links

It's early days and I'd genuinely love feedback — what's missing, what would make this a no-brainer for your workflow? If it saves you some time, a ⭐ on GitHub helps a ton. Cheers!

Short version (comments / smaller subs)

Built a free, open-source tool to break Lovable/Supabase cloud lock-in: aspire.love generates a .NET Aspire AppHost that runs your entire stack (Supabase + edge functions + frontend) locally with one command — then deploys the same solution to Azure, Kubernetes or Docker.

dotnet tool install -g love.aspire
aspire-love init --path ./my-lovable-app
aspire run

There's also a Fluent desktop app with a live code preview. MIT-licensed, feedback very welcome 🙏

Source: https://github.com/fgilde/aspire.love · NuGet: https://www.nuget.org/packages/love.aspire

reddit.com
u/Nk0BaNaNE — 4 months ago