What if the torturer put you in a dark room with a bunch of steel IKEA furniture and bedfames, (no mattresses) and a heated floor with 2 zones (only 1 is on at a time) so that you would have to either brave the gauntlet of IKEA to keep your feet warm or tell them what they want to hear?
I like this idea in concept. However in most cases failure is mostly due to power loss. So unless these seprate systems have different power sources it might not protect from catastrophy that much.
As some one who does aquaponics at home. Here are some things ive learned which you might consider.
For these reasons, I use aquaponics more as a backup and complimentary grow system to my no till regenative garden. Having an indoor system is great in the winter if you want leafy greens or to proprpgate trees for the next season.
Its not new tech but you’d most likely only see this in a datacenter or buildings with 10 Gb connections as this is fiber optic cabling. One would need an SFP to actually connect it to the port however. Also the tips of the fiber were probably scratched when installing it into the vent holes so the whole cable will probably be replaced and then fixed, so there are multiple failures here.
This is what an SFP looks like.
You could probably make a new issue in a wishlust repo that uses markdown checkboxes or something similar. Would be good if you already host Gitea or another git sever.
This is probably a good portion of return to office mandates too, this and wage theft from having less stocks elegiable to vest due to people quiting
In TBD, it’s not a “release” until its production ready. The methodology and philosophy doesn’t prevent you from developing multiple feature branches at once or even deploying a work in progress feature branch to a dev environment.
All TBD requires in that case is once the feature branch is production ready, it’s merged to the trunk. You may need to add a feature toggle if there are multiple release like for different architectures. And you also might benefit from using git tags and deploying to production from a git tag instead of the most recent commit on a branch.
Exactly what you need to do is going to depend on the project’s exact needs but TBD is totally possible in that example.
I recommend adding ollama under the artificial intelligence tag.
I don’t see the problem really…but once it becomes “Futurama did it”, I will hope to not live on this planet anymore.
Too bad the phrase fork bomb is already taken
You are right. But proxmox and many of the other suggestions aren’t vms either.
If you are dipping toes into containers with kvm and proxmox already, then perhaps you could jump into the deep end and look at kubernetes (k8s).
Even though you say you don’t need production quality. It actually does a lot for you and you just need to learn a single API framework which has really great documentation.
Personally, if I am choosing a new service to host. One of my first metrics in that decision is how well is it documented.
You could also go the simple route and use docker to make containers. However making your own containers is optional as most services have pre built ones that you can use.
You could even use auto scaling to run your cluster with just 1 node if you don’t need it to be highly available with a lot of 9s in uptime.
The trickiest thing with K8s is the networking, certs and DNS but there are services you can host to take care of that for you. I use istio for networking, cert-manager for certs and external-dns for DNS.
I would recommend trying out k8s first on a cloud provider like digital ocean or linode. Managing your own k8s control plane on bare metal has its own complications.
Changelogs are published to stakeholders. So what I’m saying is you don’t have to try to enforce a commit style using got hooks if you have public shaming at your disposal.
Because if you are creating a changelog automatically based on the commit messages it will be very public and that user will look bad.
https://www.conventionalcommits.org/en/about/#tooling-for-conventional-commits
I would say that if you are going to host it at home then kubenetes is more complex. Bare metal kubernetes control plane management has some pitfalls. But if you were to use a cloud provider like linode or digital ocean and use their kubernetes service, then only real extra complexity is learning how to manage Kubernetes which is minimal.
There is a decent hardware investment needed to run kubernetes if you want it to be fully HA (which I would argue means it needs to be a minimum of 2 clusters of 3 nodes each on different continents) but you could run a single node cluster with autoscaling at a cloud provider if you don’t need HA. I will say it’s nice not to have to worry about a service failing periodically as it will just transfer to another node in a few seconds automatically.
With a basic understanding of how k8s works and an already running cluster, all one needs to know is how to run a service as a docker file to have it also run in k8s
Well the kubernetes API has all the necessary parts built in mostly, although sometimes you may want to install a custom resource which often comes with complex service installs.
But I think the biggest strength of kubernetes is all the foss projects that are available for it. Specifically external-dns, cert-manager, and istio. These are separate projects and will have to be installed after the cluster is up.
You can also look at the cloud native computing foundation’s list of projects. It’s a good list of things that work well.
Caution, not all cloud providers support istio. I know that Google’s GKS doesn’t, they make you use their own fork of it
I would also recommend you avoid helm if possible as it obfuscates what the cluster is doing and might make learning harder. Try to just stick to using kubectl if possible.
I have heard good things about nomad too but I have yet to try it.
You should try out all the options you listed and the other recommendations and find what works best for you.
I personally use Kubernetes. It can be overwhelming but if you’re willing to learn some new jargon then try a managed kubernetes cluster. Like AKS or digital ocean kubernetes. I would avoid managing a kubernetes cluster yourself.
Kubernetes gets a lot of flack for being overly complicated but what is being overlooked with that statement is all the things that kubernetes does for you.
If you can spin up kubernetes with cert-manager, external-dns, and an ingress controller like istio then you got a whole automated data center for your docker containers.
Checkout ollama.
There’s a lot of models you can pull from the official library.
Using ollama, you can also run external gguf models found on places like huggingface if you use a modelfile with something as simple as
echo "FROM ~/Documents/ollama/models/$model_filepath" >| ~/Documents/ollama/modelfiles/$model_name.modelfile
Baseball ball mouse