- 0 Posts
- 6 Comments
If you are going to use your desktop, I would suggest putting all of the self-hosted services into a VM.
This means if you decide you do want to move it over to dedicated hardware later on, you just migrate the VM to the new host.
This is how I started out before I had a dedicated server box (refurb office PC repurposed to a hypervisor).
Then host whatever/however you want to on the VM.
Very loosely it would act as a caching or proxy service from what I understand.
My understanding is that when you subscribe to community “x” on server “y”, that your server “z” starts to download all of the content from that community so it can serve it to you locally. I don’t know how fast the activitypub protocol would fetch new posts/comments, if it’s real-time, or some kind of intermittent pull or push.
Yes, it’s a bad idea to do it this way. The most likely time a RAID array will fail is during a rebuild as that is a whole bunch of drive activity over a sustained timeframe.
Better to perform a backup or copy, power down, remove all the old drives, install the new ones, power back up, configure a new array (most people recommend to use RAID 6 at a minimum, no hot spare, so you have two drive redundancy) then restore or copy back the data.
This way you can also keep the old drives as a cold backup of sorts, potentially reimporting the configuration if needed.
In very basic terms, and why you want to do them:
Attack surface is the ports and services you are exposing to the internet. Keep this as small as possible to reduce the ways your setup can be attacked.
Network topology is the layout of your home network. Do you have multiple vlans/subnets, firewalls that restrict traffic between internal networks, a DMZ is probably a simple enough approach that is available on some home grade routers. This is so if your server gets breached it minimises the amount of damage that can be done to other devices in the network.