mprweb VS tilt

Debian has the MPR https://mpr.makedeb.org/

https://mpr.makedeb.org/ this is the link.

I know the MPR is a thing, but I've always found it unwieldy to use.

So the main difference from something like MPR is that it does that same thing, but for more packages, not only .deb files?

Regarding system repositores, it's generally best to avoid tampering with system repositories like this because it'll cause problems with release upgrades down the line. But if you really want to, look into https://mpr.makedeb.org/ with the expectation that a release upgrade with these packages installed will most likely fail.

makedeb - Like makepkg, but produces installable *.deb files. There are already lots of packages in the MPR

Actually exists! https://mpr.makedeb.org/

Mist is powered by the MPR, an AUR-like repository that's also for Debian and Ubuntu based systems (of which I'm also the project lead for, as well as the makedeb project listed below). In short, it uses pretty much the same PKGBUILD format that you'd see on Arch Linux, but uses them to build .deb packages instead of Arch Linux packages.

Could improve that crappy feedback loop :)

If the language runtimes are compiled you can't do this, but if not, in theory you shouldn't need such a stupidly long core development feedback loop.

I'm a huge fan of https://tilt.dev/ and the possibilities it unlocks for that pre-commit development.

Something like https://tilt.dev/ where you spin up a subset of the service graph in a cloud environment that hot-reloads based on local edits.

To get a similar experience of preevy up, first we’ll need to split the build and deploy using process or alternatively employ tools that orchestrate build-tag-push-update-sync flow like Skaffold/Tilt.

It's not a direct competitor, but we use https://tilt.dev/ at my company for local and remote development.

For local testing you use tilt that runs stateful services locally in a kind k8s cluster. That same config can deploy to a remote k8s server to easily share a preview of new features, which is useful for prototyping things that might not necessarily ever be merged.

There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com

You basically start by downloading kind, then tilt. Then create a kind cluster with the provided configuration in the tilt repo. Then run tilt up and that's it. You'll have a fully functional Kubernetes cluster and project running complete with deployments and services. Nothing too fancy, no RBAC, no network policies etc.. Just the bare minimum to get you up and running.

I recommend also looking into tilt.

Second, and perhaps the best of all is, that I created a tilt repository located here.

But apart from the other "k8s in a box" options (like minikube, k0s, ...) you could also have a look at tilt (https://tilt.dev/), it sounds like this might be a good fit for your use case as well.