go-getting-started VS dotfiles

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.

NixOS. If you still need Docker you can define and manage that via Nix too. I love it, both for this and managing development environments. Happy to answer any questions.

With Nix we have a shell.nix in the root of our repo describing all of the project's system dependencies. It looks something like this. You can pin nixpkgs with Flakes (think lockfiles) or by hardcoding a specific revision. We do the latter because I didn't want to complicate the Nix install for everyone by requiring they enable experimetnal features.

Nix, for example updating from rls to rust-analyzer.

I agree that the documentation story could be better. I also think it's a great shame that the language isn't statically-typed, so to understand how to use something I have to inspect its source code.

I've found it to be quite flexible though. For example, here's a commit in which I apply a patch to a tool to solve a problem that the derivation hadn't taken into account (and absent a home-manager solution): https://github.com/samhh/dotfiles/commit/867dd3b4d4b3942a0aa...

You may like to look at my newsboat config. It's biased towards FP and Linux.

Sure thing, I manage it in my dotfiles repo here.

I wonder if you'd have better luck if you built your xmonad as a proper Haskell app and didn't use the built-in --recompile stuff. It's not Nix, but see here an example of how I'm doing that.

Here's my config: https://github.com/samhh/dotfiles/blob/master/home/.config/git/config

This is possible for quickfix, see my dotfiles commit here.