tilt-dev / tilt-dev/tilt

Auto-down CLI Flag/Setting

Open
#5,210 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

duplicate enhancement
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Describe the Feature You Want

I'd like an option so an interrupt to tilt up automatically invokes tilt down.

Perhaps something like:

$ tilt up --auto-down

(And also an option to make this the project- and/or system-wide default so the user doesn't need to specify it each time.)

Current Behavior

Even after tilt up is killed, there are a bunch of running Docker containers (at least when using the docker_compose directive.)

Why Do You Want This?

My laptop battery has been draining quickly because I didn't realize/expect tilt to require me to run tilt down (or the more extreme docker ps -q | xargs docker rm -f) until a few days into using tilt.

Our Tilt stack is cheap/quick to bring up fresh, but expensive to keep running in the background so if you're done with development on Tilt managed services for the day, it's nice to not have docker wasting resources in the background, and—we're human—so it's easy to forget to run down while it's easy to remember to kill an open terminal window.

This is by no means a blocker, but would definitely be nice! ❤️🎉

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the tilt up and tilt down CLI entry points, then trace how the docker_compose directive manages containers and how project or system settings are loaded. Done means an interrupt to tilt up can trigger cleanup, with the requested command-line and default-setting behavior defined and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
cli, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.