bazel_compose VS telepresence

While this is great for people with a fundamental understanding of containers and your prod environment this will usually lead to some issues with developers that don't need to, or want to, have context in these areas.

In the past, to make a very similar workflow possible, I've built tools that automatically watch your source files and rebuild & restart only what is needed [0]. This was built for bazel + docker-compose but there isn't a reason one couldn't watch the "build:" contexts for what files are important.

At a previous company one of our engineers was a huge fan of this volume mount approach and every single time something broke (which was very frequent due to some prod/dev env magic we had) I had to assist quite a few more junior devs figure out what was wrong with their machine. For those with scripting languages, was it their system's newline endings? For compiled languages, was their system SDK different then what was in the container? For prod bugs, did they forget to rebuild & test the container before opening their PR (we had no automated integration testing)?

In my opinion, if you can make your build system in charge of building/packaging things you'll have a much happier time.

[0] - https://github.com/CaperAi/bazel_compose

Solutions are many, and could include Docker Compose, VS Code dev containers, Telepresence, Localstack or setting up temporary AWS accounts as a development environment for serverless applications.

I trialled Telepresence[0] for my company 2 or 3 years ago, that does this sort of thing very slickly. It didn't quite work for us back then, I forget why, but I imagine it's come along a way since then.

[0] https://www.telepresence.io

How does this compare to Telepresence?

seems to be very similar to https://www.telepresence.io

If they're web services you work on, you might try https://www.telepresence.io/ (Requires something to be installed in the cluster though, easily done).

Depending on the context, the type of code you do, you may want to also look into the sister protocol to LSP, DAP—debug adaptor protocol. It really depends on your context whether local dev, dev against a remote server, and if the latter whether you run under GCP and thus have the “Snapshot Debugger”, or under Kubernetes with something like Ambassadar/Emissary and thus can run Telepresence, whether you do local or remote Docker and thus most IDEs don't necessarily magically work especially if the containers are competently locked down, etc.

If you're on Kubernetes remotely, Telepresence [0] might be worth a look.

[0] https://www.telepresence.io

Sounds Like Telepresence (https://github.com/telepresenceio/telepresence) which intercepts traffic to a service on the cluster and directs it to your local environment.

This seems to be very similar to Telepresence, which I just couldn't get to work for us.

What the difference with okteto and telepresence ?