devbox VS tilt

How does Flox compare to Devbox? https://github.com/jetpack-io/devbox

I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox).

Local dev, cloud dev, CI, production – all with the same config file. Fingers crossed my talk submission for PackagingCon gets accepted. It'd be awesome to share this new way of working with a wider audience.

> Now to figure out what a "flake" is…

Flake is a worthwhile addition to Nix that is worth learning. But like anything Nixian, it's not straightforward.

Have you checked out any of the tools that aim to simplify Nix experience? We built Devbox (https://github.com/jetpack-io/devbox) with this in mind.

Also devbox ( https://github.com/jetpack-io/devbox ) which is what this is for does not work on windows because of its Nix dependency.

For these reasons, I believe most developer environments should prioritize developer experience over fidelity. Tools like Containerized development environments and cloud emulators can strike the right balance and there’s no surprise that we see increased activity around devcontainers, and similar solutions.

Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups.

We need to support local dev environments first, with the exact same config a developer can then move to the cloud.

See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in this space.

If you like the properties of Nix, but find it confusing, you should check out Devbox! It simplifies the process of creating Nix-powered dev environments:

https://github.com/jetpack-io/devbox

As part of the work we've been doing with [devbox](https://github.com/jetpack-io/devbox), we needed a unit testing framework to test some of our nix code. Unfortunately we had some use cases where we did *not* want to introduce a dependency on `nixpkgs` (and therefore we couldn't use `runTests`).

You might be interested in Devbox (http://jetpack.io/devbox)! We built Devbox because we were frustrated with our Docker based dev environments, and our goal is to provide the power of Nix with a more accessible interface (similar to yarn or other package managers).

We're open source and rapidly adding features, you can check us out on Github at https://github.com/jetpack-io/devbox

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.