Live reload reloads the container command in 2nd and other containers based on the image
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Enhancement request
When we are using some non-compiling language, like Python or Ruby in developer mode, the most part of the tools do all the changes on the fly from the box. This is the main use case of this enhancement.
Having in Tilefile
docker_build("name", "path", dockerfile="path/Dockerfile", live_update=[
sync('./path/lib', '/app/lib'),
])
...
Tilt is in watch mode with tilt up.
Regarding the Update control feature i have 2 options here. Will to throw both.
k8s_resource('name', trigger_mode=TRIGGER_MODE_AUTO). Then after each change container restarts. When the container starts more than 10-15 seconds it may be annoying.k8s_resource('name', trigger_mode=TRIGGER_MODE_MANUAL). Then i have to to the restart manually.
But what if developer do not want to restart the container and want only sync files (and let other tools to support them)?
It is a special mix of TRIGGER_MODE_MANUAL feature (because sometimes you may require to restart the container) and just sync.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Tilefile example using docker_build(), live_update, and k8s_resource() alongside the existing Update control behavior. Compare TRIGGER_MODE_AUTO and TRIGGER_MODE_MANUAL while running tilt up, and determine how a sync-only mode should behave. Done means changed files sync without restarting the container, while manual restarts remain possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100