Find me on Mastodon too.
Backblaze is a great backup solution. They publish drive stats and even show you the hardware they use.
https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data
https://www.backblaze.com/cloud-storage/resources/storage-pod
boom
Oblig. XKCD:
Try using 1.1.1.1 or 8.8.8.8 as the external DNS in your router for testing. Does it work then?
Also, you may have DNS cached somewhere. You can flush your Windows DNS cache by typing ipconfig /flushdns in a command prompt.
Fuckin autocorrect was the death of us all.
tar --help
spawn(newTimer, 1000)
You can host overseas and use a proxy for hosting. I mostly don’t worry about it though because I don’t do anything illegal.
Use encryption if you are concerned.
I’ve used Hyper-V and in fact moved away from ESXi long ago. VMWare had amazing features but we could not justify the ever-increasing costs. Hyper-V can do just about anything VMWare can do if you know Powershell.
Here’s a quick method:
Get the IP and set up the dns for the new server. Get a cert via Let’s Encrypt or self sign to get ssl working, and then start your prep.
On the new host create the new directory structure. Note your folders, paths, and permissions. Set the permissions on the pictrs folder as 991 (sudo chown 991:991 /path/to/pictrs/folder even if that user doesn’t exist on your system. It’s for the container.
You’ll need to edit your yml files, docker compose file, and make sure that the paths are updated, the instance name is correct, and federation is disabled (until testing is done).
Copy pictrs and db folders from old host to new. You can skip pictrs if space is a concern, but you’ll lose your instance pics.
Once done, copy over the containers and bring them up.
Check for errors and diagnose as necessary.
Once set, change the federation to on, switch your dns from old server to new, and then perform another sanity test.
I’m doing what you want to do now. I’m running lemmy.fan on a NAS with really good hardware on a fiber connection. My ISP provides symmetric bandwidth and doesn’t block anything, though emails can’t be sent with a local smtp server since most places don’t trust the IP addresses of residential subscribers.
I learned a ton, I’m enjoying running things, and though it’s an open instance I don’t advertise it. I say go for it. Experiment and have fun. If it sucks and you hate it you just stop the containers.
Poor skill, mostly.
Reminds me of a comment I once came across in a work application’s code: “This function took forever to write correctly. It was hard work. I didn’t document it. Figure it out.”
Of course the variables were not defined properly and were named esoterically.
Still true though. I’m distro-agnostic, running the best whatever for the job at hand.
When I give a presentation at a conference about something technical, the question always comes up: “Why are you running that on so-and-so? $Distro is so much better…” and their whole train of thought deviates from the subject at hand.
Point is, the tool is the tool. If Fedora is the best option given our licenses and use scenario, I don’t need to hear about how much better xyz is and how we’re wasting money.
I just want xyz to work. I don’t need the distro wars to be a thing when I’ve got 6 other more important things to attend to.