←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.221s | 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 #
Noumenon72 ◴[26 Apr 25 21:15 UTC] No.43807284[source]▶
If you have sidecar containers that feed your regular containers, or you need to test a Dask KubeCluster, or deploy Helm charts, this kind of lets you work with the real lifecycle. Tilt is kinda better at watching for code changes in all your containers than docker-compose too, and has a nice UI to watch logs and see what succeeded or failed.
replies(1): >>43807349 #
1. cirego ◴[26 Apr 25 21:23 UTC] No.43807349[source]▶
Tilt can also help validate things like:

- Service discovery

- Volume mounts

- Ingress and Certificates

- Metrics scraping and configuration

- Dashboards

It’s really quite powerful and replaces the need to mock things out with docker compose. If you’re deploying to Kubernetes, Tilt gives you the option to avoid “development-only” setups like docker compose.