Using USB3 / USBC external storage for years.
Buy a good, non cheap, USB jbod or raid enclosure and put SSDs in it!
I have a 4 bay USB3 jbod plus a 2 bay USB-C box, inside the disks are all RAID.
Indeed internal disks / ssds / nvme are better, but consider that speed wise even USB3 is faster than any WiFi.
Just don't but they cheap and use good cables. And if you use spinning disks, ensure they stay cool.
Yes it counts indeed... But in that case the service is down while its migrated so the fact the database is also down does it count?
I mean, it's a self hosted home service, not your bank ATM network...
Absolutely! If that feels easier and more consistent go ahead and use the container.
But its really one single executable with zero dependencies. Manual setup is really as fast as podman pull & up -d.
Yes exactly, you can switch as fast as your DNS entry gets updated and you have zero dependency to a specific provider.
No, I mean, do host on your own hardware then rent a vps and use it as public IP by ssh-tunneling and forward ports 80/443 back to your own hardware.
The idea is: https://wiki.gardiol.org/doku.php?id=selfhost:architecture
I have rented a cheap vps and use ssh encrypted port fotwarding to it instead of cloudflare. Its an option in alternative.
Why would that have blocked all my databases at once? That would affect the same database I was migrating, not the others.
I fully agree with you that devs should not release debs&rpms&etc, that's distro responsibility to create and manage from the binaries that the devs should release. No Dev should have to create those distro-bases formats, it's evil and useless.
Let me be more clear: devs are not required to release binaries at all. Bit they should, if they want their work to be widely used. And in this case, providing also a binary release alongside images solves all freedom of choice issues in my opinion. Here you show me my lack of preparedness as I didn't considered docker files as actual build instructions, I will do in the future.
I also fully agree with you that curl+pipe+bash random stuff should be banned as awful practice and that is much worse than containers in general. But posting instructions on forums and websites is not per se dangerous or a bad practice. Following them blindly is, but there is still people not wearing seatbelts in cars or helmets on bikes, so..
I was not single containers out, I was replying to a post about containers. If you read my wiki, every time a curl/pipe/bash approach is proposed, I decompose it and suggest against doing that.
Chmod 777 should be banned in any case, but that steams from containers usage (due to wrongly built images) more than anything else, so I guess you are biting your own cookie here.
Having docker files and composer file is perfectly acceptable. What is not acceptable is having only those and no binary releases. Usually sources are available (in FOSS apps at least) but that can be useless if there are no building instructions provided or the app uses some less common build stack.
On Immich, which is a perfect example of an amazing piece of software fast growing and very polished, I did try to build from sources but I couldn't manage the ML part properly. This is indeed due to my lack of experience with the peculiar stack they are using, but some build instructions would have been appreciated greatly (now I realize I should have started from the docker files). I gave up and pulled the images. No harm done, but little extra fun for me, and while I do understand the devs position, they too keep talking about making a living out of it and that's a totally different point to discuss on a different thread. I would suggest them that public relations and user support is more important than actually releasing an amazing product for making a living out of it. But that's just my real world experience as product manager.
In a world where containers are the only proposed solution, I believe something will be taken from us all. Somebody else explained that concept better then me in this thread. That's all.
Radicale is a single executable, do you really need docker to set it up?
Basically takes the same time to set it up and run on bare metal...
Sometimes feels like docker is getting out of hand.
Now that you have an UPS, put reminders on changing the batteries. My experience with both high end professional units and low cost home units is that batteries last two years more or less and can be expensive to replace.
Having an ups is great, having it fail unexpectedly because the battery packs go from 100% to 1% instantaneously as soon as a load is applied, not so much
I might have been unlucky, but I had mine fail always at the worst possible moment and without the slightest warning.
My current solution is a laptop (but look out for bulging batteries!) And ups backed USB (not cheapo ones!) Jbod or raid enclosures. In this cas e a 50€ battery pack is enough for a brief power outage.
I put my 2.5 ssds with adapters into 3.5 bays