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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.
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
I use powetop on laptops to recommend config optimizations, it could run on a server too.
hdparm can configure HDDs to powerdown, but I've never had any success using it on my router.
In theory I think You could use WoL and have your router wake a device before sending traffic but I haven't seen any guides for doing this so maybe I'm missing something.
WoL works, but your server will take some time to come back online, but the router probably wont be able to buffer the traffic for that long, and a tcp connection would likely timeout before then anyway. You usually want to send the WoL magic packet, wait for the server to come back online, and only then start sending traffic.
What's the timeout on a TCP connect?
Could you not wake from suspend in that window? Maybe even a full hibernate?
The TCP connection time out on linux defaults to a bit over two minutes, although individual client programs can use different values, and I'm assuming Windows is similar. Honestly, I was thinking about the time to boot a server, but if you're just suspending you'd almost certainly be ok, albiet with a slight power draw even when the machine is not in use. Hibernating might also be ok as long as your hardware gets through its POST quickly.
Working on this. Cron to power off the server in the evening, and WOL from my standalone pFsense box to the server to power up with etherwake.