←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 1 comments | 26 Apr 25 19:14 UTC | HN request time: 0.208s | source
Show context
siliconc0w ◴[26 Apr 25 21:37 UTC] No.43807429[source]▶
You're always trading off speed with fidelity. Usually, trying to maintain a local integration environment is going to become too slow and expensive. The problem isn't even necessarily Kubernetes, but as dependencies increase it just gets slower and slower to try and run a copy of the world locally.

I like a fast svelte dev environment with something like docker-compose which might require some mocked out dependencies to keep things fast and then using Kubernetes for other environments once I have local tests passing.

replies(2): >>43807630 #>>43816909 #
1. hdjrudni ◴[28 Apr 25 02:18 UTC] No.43816909[source]▶
You can always swap out some of those services for always-running prod or dev-in-the-cloud services.

I have a big mix of setups for my projects. I like Vite+Bun (client+server) for smallish projects because the dev servers start instantly. But then I have to remind myself how to actually productionize it when it comes time for that, but it's not too hard.

Then sometimes I need to bring in a database. I don't like running those locally, undockerized because now you're locked into one specific version and it just gets messy. So sometimes if I'm lazy I just connect to my prod database server and just create a separate dev DB on it if needed. Then I don't need to start and stop anything, I just connect. Easy.

For a big complex app you can mix-and-match any of the above. Run the services that you need to iterate heavily on locally, and just farm out the rarely changing stuff to the cloud.