Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tilt: dev environment as code

github.com

Post reply on HN
Print view View original

11–20 of 67 posts

Re: Tilt: dev environment as code

#11

Post by cirego »

Szpadel wrote: post #7
sigmonsays wrote: post #4

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?

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.

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.

Re: Tilt: dev environment as code

#13

Post by cirego »

satvikpendem wrote: post #5

Isn't this essentially dev containers?

My understanding is that dev containers are more about configuring your development environment with the right toolchains to build and run services.

Tilt is a monitor process that builds and starts your services, with a hot-reload loop that rebuilds and restarts your services when the underlying code changes. The hot reload loop even works for statically compiled languages.

Re: Tilt: dev environment as code

#15

Post by dhorthy »

Been using tilt as a make alternative for years. Great tooling, even as just file watch + pythonic syntax for running tests, etc.

Obvs the real magic is the live syncing patches into remote containers though

Re: Tilt: dev environment as code

#16

Post by siliconc0w »

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.

Re: Tilt: dev environment as code

#18

Post by turtlebits »

patwoz wrote: post #17

How does Tilt compare to “skaffold dev“? We use skaffold exactly for that purpose. To develop within a the cluster.

Skaffold works but its DX is pretty poor. Too many knobs via yaml- tilt has just enough magic that it doesn't feel like a chore to setup local dev.
Post reply on HN