Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
You could use a very low power computer that's always on like a Raspberry PI Zero W to send the WoL packet to the backup computer. It only uses about 1 watt. Some routers have the ability to send a WoL packet as well.
And how do you communicate with the Pi0?
Use SSH. Ether open a port in the firewall or connect it to a VPN. If the backups are done on a schedule, you could also setup a cron job on the Pi to send the WoL packet a few minutes ahead of time.
Use a VPN; don’t open up SSH to the internet.
Or just be cautious, thoughtful and sensible if you do. Only a Sith deals in absolutes.
Ssh over Internet is fine as long as it's properly setup (no password auth, root not allowed, etc.). Obviously a VPN is even better.