←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 2 comments | 26 Apr 25 19:14 UTC | HN request time: 0.443s | source
Show context
sigmonsays ◴[26 Apr 25 20:58 UTC] No.43807159[source]▶
i don't get the value of a tool like this.

Do we really struggle bringing up services as containers and applying kube configs?

For my development of services that run in kube, I don't dev with kube, you shouldn't have to. I also use docker-compose for most dev env services.

Perhaps i'm not developing the right kind of software. Whoever finds this type of tool useful, when would you use it?

replies(6): >>43807259 #>>43807284 #>>43807739 #>>43807754 #>>43810454 #>>43816940 #
eats_indigo ◴[26 Apr 25 22:22 UTC] No.43807739[source]▶
I think if you ever have highly dynamic infrastructure requirements -- think along the lines of a control plane that's spinning up additional workers -- it's really helpful to be able to run your infra provisioning logic locally. There's nothing worse than having to wait on cloud builds to test your iterations.
replies(1): >>43810350 #
oulipo ◴[27 Apr 25 08:24 UTC] No.43810350[source]▶
What would be the difference between eg Tilt and Pulumi for this?
replies(1): >>43810406 #
1. dharmab ◴[27 Apr 25 08:39 UTC] No.43810406[source]▶
Tilt is for your laptop, where you're editing code. Pulumi is for your cloud environments.
replies(1): >>43815143 #
2. oulipo ◴[27 Apr 25 21:07 UTC] No.43815143[source]▶
I can use Pulumi on my laptop too... that's precisely what I do... for my use-case I use it more like a "programmable docker-compose" if you want