go-getting-started VS telepresence

Air for live reloading https://github.com/cosmtrek/air, Teller for env and secret manager https://tlr.dev, Okteto cloud development https://www.okteto.com

https://tilt.dev/ or https://www.okteto.com/ could probably do what your looking for to a degree

I created a Dockerfile and docker-compose and uploaded it to [okteto](https://www.okteto.com/), I now have a running instance of my rasa bot here in a URL similar to: https://my-server-username.cloud.okteto.net. However, if I try to access it via postman I get a 404.

Ya'll should consider https://www.okteto.com/ too.

Okteto is an application that allows you to develop inside a container, along with many features it permit the user to start a development environment and provide an automatic SSL Endpoints for k8s.

What the difference with okteto and telepresence ?

Hey! Recently, I’ve been playing around with [Okteto](https://www.okteto.com/) to see how it helps with the local development of apps that will run in Kubernetes. It seems to be quite a good option for developers who don’t want to spend their time dealing with setting up and maintaining clusters. Moreover, you can use a development environment from Okteto without thinking about CI/CD pipelines for delivering the app.So, instead of working on your code locally and deploying it then to the cluster, the whole development process is shifted straight to K8s. That makes Okteto approach a bit different from what other projects, like Skaffold and werf, do. To implement this idea, they offer a [CLI tool](https://github.com/okteto/okteto) and their own cloud provided as both SaaS and self-hosted (it has a limited free option).Here is [my overview](https://blog.flant.com/okteto-cloud-for-local-development-in-kubernetes/) of Okteto; any feedback — especially, your own experience — is more than welcome.

We use something called Okteto to see local react changes running against a fairly complex Kubernetes setup. Not sure if it will suit your needs but it works well for us ATM.

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 ?