←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 2 comments | 26 Apr 25 19:14 UTC | HN request time: 0.521s | source
Show context
patwoz ◴[26 Apr 25 21:42 UTC] No.43807456[source]▶
How does Tilt compare to “skaffold dev“? We use skaffold exactly for that purpose. To develop within a the cluster.
replies(3): >>43807561 #>>43807733 #>>43807748 #
1. lima ◴[26 Apr 25 22:23 UTC] No.43807748[source]▶
Much more flexible than Skaffold thanks to Starlark config vs. a rigid YAML structure.
replies(1): >>43808933 #
2. ajayvk ◴[27 Apr 25 02:13 UTC] No.43808933[source]▶
Starlark does allow for much more concise and powerful config specification. I am building https://github.com/claceio/clace, which is an application server for teams to deploy internal tools.

Clace uses Starlark for defining apps, instead of something like YAML. https://github.com/claceio/clace/blob/main/examples/utils.st... is a config file which defines around seven apps (apps are downloaded and deployed directly from git).

Clace uses Starlark for defining app level routing rules also. This avoids the need to use a nginx like DSL for routing.