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:
- 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
It allows me to connect into the house via the VPS without opening ports or knowing my home address.
Nowadays there are various companies offering tunnelling services, but my setup has been working for a long time and I see no reason to change.
I clearly don’t know enough about reverse ssh connections.
My understanding is that you tell the VPS to connect to your computer, a shell pops up on your end, and commands run in it will control the VPS. It helps get around firewalls and makes it less obvious to defenders that an attacker has control of a box because it’s not an inbound connection, it’s an outbound connection.
What’s your workflow? So you ssh into the VPS and maybe use Tmux or Screen to connect to a terminal session, that session is connected to your home machine but instead of sending commands back to the VPS, it sends commands to your home computer?