First find a way to track your costs. Measure how much it costs to give it away (to your self and people that support you starting it as a buisness). Do market analysis based on those number. How much do you need to support both your operatiinal costs of hosting and devoloper time paid with a fair wage, and what does compare to how much consumers are currently paying. If that looks good invest in an accountant and lawyer to see what the buisness plan viability might look like and set up a LLC. From there look for partners that can help you create a sustainable buisness and fill in skill gaps you dont have, or hire out the rest.

Thats it.

Even better make it a community coop so that the skilled labor and community can have actual ownership in the org to help balance out thr risk and encourage litteral buyin.

One idea that I think would be neat would be to expand it beyond written texts. For example: https://chewydecimalsystem.org/

I am somewhat biased in this regard too though, while physical location has to be tied to a singular thing, with digital mapping tag systems, even better if they are scalable, make for much more accurate catalogs.

For example the arch wiki is a reference source, but of what info? Hierachical stacking helps but falls apart when now the gaming sections of the arch wiki can’t be found next to the Windows gaming sections because they are isolated by OS instead of by gaming, or you are digging through every OSs collection of gaming information when you do have an OS specific question.

I use VMs for OS isolated and hardware isolation. I run containers on top of OSs for apps.

That said I use Harvester so I can run containers on bare metal AND VMs as containers.

Even on one bare metal I do this, so I can spin up a test VM of harvester to confirm configs. If you one node is super beefy a neat trick is to have VMs running a cluster so you can have a kind of high availability even if your infra is a single point of failure.

Mermaid.js and UML has covered what I thought were some pretty complex systems diagrams myself

Rancher Desktop?

K3d?

Or something else?

CloudNative PG is so far my favorite. I also prefer a PG per App.

Fosai@lemmy.world would probably be a good place

I’m imagining some script that only functions based on the angle/position of the rats spin

Dockers permission structure AND service running as root really does baffled the mind sometimes

Gentle reminder that there, in fact, much better ways to deploy containers.

I really enjoy the pikvm and the switcher for my home lab. Redfish support gets fishy with a switcher if that is a concern though.

I do love a good mesh for a cluster block though. My next next next project is using KubeOVN to turn my cluster block into a switch with “out” connections to connection other devices (wifi, laptop, cameras, etc) to it as my network router and of course upstream from the modem and hotspot for Internet connection.

I would recommend 4-5 nodes. 5 if you want true high availability. 4 still requires some intervention in case of failure.

Just because it’s bare metal. Got to think of your Mean Time to Repair (MTTR) which is to say if a whole node goes bust how long will it take to potentially order and install a new one.

If you go kubernetes (k8s) I would recommend rke2 or k3s. They are really straightforward setups and pretty enterprise ready out of the box.

If you have a hard requirement for Ceph I would recommend doing Rook-Ceph which makes deploying and management a lot easier by letting k8s handle it. For simpler but less performant (in my testing) persistent volumes (PVs) like ceph Longhorn is really easy to deploy and manage.

For backups Velero is really nice for apps in your cluster, since it can be done per namespace and include PV data too. Rke2/k3s both have nice etcd (the backend data base for k8s) snapshoting and backup tools too for full disaster recovery.

Rke2/k3s both have ways to auto deploying charts from the filesystem too https://docs.rke2.io/add-ons/helm

This is a good stepping stone for GitOps imho. If that matters to you at all. Starting with just having a git dir for these files, then later doing some like ArgoCD

I would also recommend, since you are looking at hyper converged storage have dedicated network lines for it is generally recommended. So create a bond of two ports per node just for storage, tag them with their own vlan, and in your setup of rook or longhorn specific that vlan interface as the device for data to flow.

Pxe boot is also nice at this scale, either setup on your router (OpenWrt has decent support), you maintance laptop/machine, and/or do something like Tinkerbell (cloud native pxe from your k8s cluster!). It’s just nice to be able to blow away a node and rebuild if you are tinkering a lot.

Remember cattle not pets, and welcome to the range cowpoke!

The pikvm and pikvm switch are really fun tbh

I mean even more options there like Longhorn or Rook-Ceph

That would be the second. The first would cover the right to share information about building your own uncensored 3d printer and designs and plans for legal arms.

Im.very into “AsCode” and pretty comfortable with vi bindings. So the two extremes where i document (random notes with no structure needed and formally verified documentation ) it works for me.

I can preview the markdown, use vale rules to enforce style and vocab, do mermaid.js diagrams, link my UML to stuff, etc.

Then check into git to do version control or just to save it off local.

The silence of two hours ago lol

Chill brother. Like i get it, and FOSS advocates should lead with meaningful alternitives first imho, but there definitly seems to be some https://joplinapp.org/

I personally prefer vscodium and nvim myself for notes but that isnt a one for one comparison to obsidian (in either direction) imho

https://joplinapp.org/

Seems interesting

Im a VSCodium kind of guy myself

I have my shared data on Longhorn, so for services that’s just longhorn as a PVC on rke2(k8s) and for clients I expose the NFS for mounts from a longhorn PVC to them to mount to.

How is the kubernetes (k3s/rke2) migration coming along?

Why not cloudinit instead of ssh?