←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.486s | 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 #
1. Szpadel ◴[26 Apr 25 21:11 UTC] No.43807259[source]▶
I never used tilt, but it looks very useful for anything that needs kube API to work, like some operator or something that needs to discover configuration from config maps.

otherwise I think it's meant for systems where system that you need for testing is to big to work on your local machine.

replies(1): >>43807366 #
2. cirego ◴[26 Apr 25 21:27 UTC] No.43807366[source]▶
Yes, Tilt really shines when you’re testing interactions with Kubernetes, such a APIs. But also things like your services’ ingress configuration and metrics scraping.

By default, Tilt is actually intended for local development using kind, minikube or other similar tooling. It supports developing against a multi-node cluster but it requires extra configuration and slows down iteration time.