problem-diagnosis-remedy-proposal
A clear, generally concise proposal format to win hearts and minds (by colindean)
tilt
Define your dev environment as code. For microservice apps on Kubernetes. (by tilt-dev)
problem-diagnosis-remedy-proposal | tilt | |
---|---|---|
1 | 49 | |
8 | 7,319 | |
- | 1.1% | |
0.0 | 8.8 | |
over 1 year ago | 2 days ago | |
Go | ||
- | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
problem-diagnosis-remedy-proposal
Posts with mentions or reviews of problem-diagnosis-remedy-proposal.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-08.
-
Should devs manage dev environments
The trick is always convincing people that there is a better way. Because you have such a small team responsible for so much, you really need to establish consensus with some discussion and counter-railroading. I push the problem, diagnosis, remedy proposal model on a lot of my organizations whenever I see that there's not consensus or that there's not much interest in consensus or shared knowledge. Sometimes a "do what you think is right" carte blanche from the team is a good thing when you want to go fast, but when you want to go far together, having written artifacts of your intentions and the reasoning behind them is incredibly important. On a small team, you do not have the luxury of isolation or compartmentalization.
tilt
Posts with mentions or reviews of tilt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-28.
-
Ask HN: What to do with small units of time during the working day?
Could improve that crappy feedback loop :)
If the language runtimes are compiled you can't do this, but if not, in theory you shouldn't need such a stupidly long core development feedback loop.
I'm a huge fan of https://tilt.dev/ and the possibilities it unlocks for that pre-commit development.
-
Uber Migrates 4000 Microservices to a New Multi-Cloud Platform
Something like https://tilt.dev/ where you spin up a subset of the service graph in a cloud environment that hot-reloads based on local edits.
-
Simplifying preview environments for everyone
To get a similar experience of preevy up, first we’ll need to split the build and deploy using process or alternatively employ tools that orchestrate build-tag-push-update-sync flow like Skaffold/Tilt.
-
Codespaces but open-source, client-only, and unopinionated
It's not a direct competitor, but we use https://tilt.dev/ at my company for local and remote development.
-
Why I recommended ECS instead of Kubernetes to my latest customer
For local testing you use tilt that runs stateful services locally in a kind k8s cluster. That same config can deploy to a remote k8s server to easily share a preview of new features, which is useful for prototyping things that might not necessarily ever be merged.
-
Local development set up for microservices with Kubernetes - Skaffold
There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com
-
First K8s project
You basically start by downloading kind, then tilt. Then create a kind cluster with the provided configuration in the tilt repo. Then run tilt up and that's it. You'll have a fully functional Kubernetes cluster and project running complete with deployments and services. Nothing too fancy, no RBAC, no network policies etc.. Just the bare minimum to get you up and running.
-
Devcontainers in k8s
I recommend also looking into tilt.
-
KubeProject: A distributed multi-service project on Kubernetes as a playground for beginners
Second, and perhaps the best of all is, that I created a tilt repository located here.
-
Throwaway preconfigured local kubernetes environments
But apart from the other "k8s in a box" options (like minikube, k0s, ...) you could also have a look at tilt (https://tilt.dev/), it sounds like this might be a good fit for your use case as well.