Tilt to live sample code how how to#

(Click the screenshot to see an interactive view.) Let’s see what this new configuration looks like in action: The result of a live_update. The third step congratulates you on finishing this guide! The second step runs our script to report the deployment time. The first step syncs the code from the current directory (. We’ve added a new parameter to docker_build() with three live_update steps. # Add a live_update rule to our docker_build.ĭocker_build ( 'example-html-image', '.', live_update = ) With Tilt, we can skip all of these steps, and instead When we make a change to a file, we currently have to build an image, deploy new Kubernetes configs,Īnd wait for Kubernetes to schedule the pod. Can we do better? Step 2: Let’s Optimize It Tilt offers you some default benchmarks, and the tools to capture your own. To schedule the process, and the time until the server is ready to serve

There are many benchmarks we care about – the time to build the image, the time If you look closely, the elapsed time displayed in the Tilt sidebar is different (Click the screenshot to see an interactive view.) Approach Let’s click the button on the deploy resource and see what happens! Clicking the button triggers the 'deploy' local_resource, which in turn kicks off an update to the server. We’ve also modified our server itself to read that start time and print the time The local_resource() call creates a local resource named deploy. Local_resource ( 'deploy', 'date +%s > start-time.txt' )

Tilt to live sample code how how to#

# shows you how to set up a custom workflow that measures it. # Normally, you would let Tilt do deploys automatically, but this K8s_resource ( 'example-html', port_forwards = 8000, resource_deps = ) # Records the time from a code change to a new process.