get a cheap N100 box. do not overspend.

:sweat-smile: intensifies

joplin -> silverbullet

happy with switch, fits my mind flow better. no folders or files.

trust us! our logos are blue and our salespeople are bald and/or buff. lol ya

what is this study? why does the article not link to it and the data? what is the sample size, located where? waste of time post, downvoted.

makertube.net, youtube is mask off at this point

https://github.com/fosrl/pangolin

use this instead of tailscale or other corporate options. tailscale is going for IPO, their service cannot survive investor greed.

just get a cheap n100 box, don’t overspend

it would be amazing if geerlingguy was the one to make youtube go mask off

ansible has a learning curve but will save you a lot of time in long run over bash.

write playbooks rhat target groups of similar hosts instead of a playbook for each distinct host, target specific hosts with -l flag of ansible-playbook.

look into molecule for testing sooner than later. helps you be more confident your plays will work as expected vs running trial and error on a host and getting it into a bad state. i run on bare metal so more important for my workflow not to wipe a folder with a typo, etc.

https://forgejo.org selfhosted has been good for me, FOSS fork of Gitea.

I run a k3s cluster for selfhosted apps and keep all the configuration and docs in a git repo. That way I have history of changes and can rollback if needed. In that repo I have a docs folder with markdown documents about common operations and runbooks.

There are other ways to do this, but I like keeping docs next to the code and config so I can update them all at the same time. Deployed several wikis in the past but always forget to update them when I change things.