31–40 of 67 posts
Single cluster deployments are very easy.
My problem is that these services we manage in production are deployed across multiple regions (or k8s clusters).
Debugging _distributed_ applications is the issue.
Why do not use well organized Makefile instead of invent new junk. Is it a product placement?
There is also .PHONY, but that would make the rule to always be triggered. Maybe I'm misremembering, it's been a long time :)
Why do not use well organized Makefile instead of invent new junk. Is it a product placement?
Can you do it? Sure, but somewhere someone is going to be suffering.
There seem to be a lot of tools in this space. I wish they wouldn't call themselves tools for "dev environments" when they are really more like tools for "deploying an app to your local machine", which is rather different.
The pitch is kinda funny to me: > Modern apps are made of too many services. They're everywhere and in constant communication. So we made tooling to make it easier for you to make more of them!
How does Tilt compare to “skaffold dev“? We use skaffold exactly for that purpose. To develop within a the cluster.
Much more flexible than Skaffold thanks to Starlark config vs. a rigid YAML structure.
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.
The pitch is kinda funny to me: > Modern apps are made of too many services. They're everywhere and in constant communication. So we made tooling to make it easier for you to make more of them!