wraith

I very much appreciate your advice. I’ll see what I can find in there.

Do you know if Vitamix motor units are relatively easy to repair? We have one that the speed control doesn’t seem to work consistently anymore. Even at low speeds sometimes it’ll randomly rev all the way to max, or if the knob is turned up sometimes it won’t actually speed the motor up. I think the model is VM0102D if that changes things.

We’ve been dealing with it as-is because the overall functionality isn’t terribly impacted, it just needs a little extra monitoring when it’s in use, but if I can fix it it’d be a much better experience.

Tbh, it's still pretty huge the funding got completely cut. And that the CPB shut down rather than leave the door open for a takeover of their legitimacy by the right-wing propaganda machine. We all need to be giving money to our local NPR and PBS stations to keep them going if possible.

Totally agree, we need to press legislators to refund public media as soon as possible, but at least stations are continuing with what local funding they can muster.

I feel obliged to point out that PBS isn’t shutting down. The Corporation for Public Broadcasting voted to shut down, but they allocated federal funding to local PBS stations so their role is now somewhat moot with the funding rescission. Local stations, and the PBS network, will continue to produce excellent programming because a majority of their funding comes from local donors, not the CPB.

I don’t think you’ll see any changes to the PBS website or archives.

I think this is a great idea. With such a foundational deployment concept like OS there are so many options and each can change the very core of one's self hosted journey. And then expanding to different services and the different ways to manage everything could be a great discussion for every existence level.

I myself have been considering Proxmox with LXCs deployed via the Community Scripts repo versus bare metal running a declarative OS with Docker compose or direct packages versus a regular Ubuntu/Debian OS with Docker compose. I am hoping to create a self-documenting setup with versioning via the various config and compose files, but I don't know what would end up being the most effective for me.

I think my overarching deployment strategy is portability. If it's easy to take a replacement PC, get a base install loaded, then have a setup script configure the base software/user(s) and pull config/compose files and start services, and then be able to swap out the older box with minimal switchover or downtime, I think that's my goal. That may require several OS tools (Ansible, NixOS config, Docker compose, etc.) but I think once the tooling is set up it will make further service startups and full box swaps easier.

Currently I have a single machine that I started spinning up services with Docker compose but without thought to those larger goals. And now if I need to fiddle with that box and need to reboot or take it offline then all my services go down. I think my next step is to come up with a deployment strategy that remains consistent, but I use that strategy to segment services across several physical machines so that critical services (router, DNS, etc.) wouldn't be affected if I was testing out a new service and accidentally crashed a machine.

I love seeing all the different ways folks deploy their setups because I can see what might work well for me. I'm hoping this series of discussions will help me flesh out my deployment strategy and get me started on that migration.