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

41–50 of 67 posts

Re: Tilt: dev environment as code

#41

Post by AYBABTME »

cirego wrote: post #2

Interesting to see this pop up here! I’ve been using Tilt for multiple years now but the pace of development seems to have slowed down after the Docker acquisition. I love how Tilt enables creating a local development environment that lets my services run the same in production , test and development. Greatly simplifies my service code and improved my quality. In particular, I’d love to see Tilt be better around hand…

Same, being able to depend on CRDs between resources would be very useful, since a lot of my Tilt usage is about making operators or working with operators.

Happy to see new releases of Tilt even if the pace has slowed down. It's a very useful tool.

Re: Tilt: dev environment as code

#44

Post by OptionOfT »

hamandcheese wrote: post #37

I still think "dev environments" really ought to be running tests directly with your languages native tool. e.g. `cargo test`, `bundle exec rspec`, etc. If you make me run a VM that runs Kubernetes that runs a docker container that runs the tests, I will be very, very upset. Doing this properly and reliably can still be a lot of work, possibly more work if not relying on Docker is a design goal (which must be if you…

Not to mention the developer experience is usually sub-par.

I firmly believe that the primary way of interacting with my tests should be the ability to run them one by one from the IDE, and running the code should be run / attach with breakpoints.

Re: Tilt: dev environment as code

#45

Post by michaelmior »

OptionOfT wrote: post #44
hamandcheese wrote: post #37

I still think "dev environments" really ought to be running tests directly with your languages native tool. e.g. `cargo test`, `bundle exec rspec`, etc. If you make me run a VM that runs Kubernetes that runs a docker container that runs the tests, I will be very, very upset. Doing this properly and reliably can still be a lot of work, possibly more work if not relying on Docker is a design goal (which must be if you…

Not to mention the developer experience is usually sub-par. I firmly believe that the primary way of interacting with my tests should be the ability to run them one by one from the IDE, and running the code should be run / attach with breakpoints.

It takes some work, but it's entirely possible to both use Docker and run individual tests with breakpoints (in a Docker container) in your IDE. For example, you can attach VS Code to a running container.

Re: Tilt: dev environment as code

#47

Post by brumar »

hamandcheese wrote: post #37

I still think "dev environments" really ought to be running tests directly with your languages native tool. e.g. `cargo test`, `bundle exec rspec`, etc. If you make me run a VM that runs Kubernetes that runs a docker container that runs the tests, I will be very, very upset. Doing this properly and reliably can still be a lot of work, possibly more work if not relying on Docker is a design goal (which must be if you…

True. I learned this the hard way.

Re: Tilt: dev environment as code

#48

Post by simultsop »

cirego wrote: post #2

Interesting to see this pop up here! I’ve been using Tilt for multiple years now but the pace of development seems to have slowed down after the Docker acquisition. I love how Tilt enables creating a local development environment that lets my services run the same in production , test and development. Greatly simplifies my service code and improved my quality. In particular, I’d love to see Tilt be better around hand…

As far as I understand, this might be is the best tool for the guy who acquires a SaaS and have no clue how to develop/tweak stuff. Again still have no clue how you enable this or do you still have tilt in production. Marketing is not a big deal for tilt as far as I understand.

Re: Tilt: dev environment as code

#49

Post by oulipo »

eats_indigo wrote: post #27
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 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.

What would be the difference between eg Tilt and Pulumi for this?

Re: Tilt: dev environment as code

#50

Post by oulipo »

campbel wrote: post #42

I did a blog post for Linkerd showing some of the benefits of using Tilt https://linkerd.io/2024/12/02/tilt-linkerd-nginx-part-1/ . TL;DR you can run some of your infra in local-dev that provide parity with your production environment.

I'm using Pulumi for this right now (with a dev setup and a prod setup), what would be the benefit for me to use Tilt over this?
Post reply on HN