Also: if you suffer from frequent power outages, you have to have a server that 'bounces back' and survives the outage, with all the necessary services up and running after a reboot. Good luck writing scripts for that scenario.
Also: if you suffer from frequent power outages, you have to have a server that 'bounces back' and survives the outage, with all the necessary services up and running after a reboot. Good luck writing scripts for that scenario.
In my experience self-hosting a number of services, it's really no more challenging than managing the services themselves. A BIOS that supports wake-on-power is obviously a key hardware requirement. On the software side, I find systemd and DuckDNS to be very helpful and easy to use.
One of my sites is a remote cabin that suffers blackouts all the time. It has the burden of an LTE connection, which means it requires an ssh tunnel to get around the ISP's firewall. This makes autossh an additional, if simple and reliable component.
Does anyone know for sure if Xfinity in Marin County, Ca allows self-hosting?
https://www.xfinity.com/Corporate/Customers/Policies/HighSpe...
This applies to Comcast's (at least residential) customers nationwide. But I, like you, get the sense that it's there so they can shut down excessive bandwidth use; I haven't heard about them trying to shut down a low-traffic webserver or self-hosted stuff for one's own personal use (though I probably wouldn't try to run a gaming server or anything high-traffic). Just be aware that it is technically against Comcast's Acceptable Use Policy, and try to switch to a better internet provider if you have the option.