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.
Resources:
- 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
How do you know you're connecting to the server you think you're connecting to? When you enter
http://myserver.local
into a web browser, for example, it does a DNS lookup to get an IP address. You're assuming that that lookup returns the value you think it should. BUT if something has poisoned your DNS cache, added an entry to /etc/hosts, etc. that IP address could be some other server. Without a certificate being presented by the server you likely wouldn't notice.But as I said - it's pretty unlikely in your scenario. But something to understand better for other scenarios.