view the rest of the comments
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
I do plan to primarily ssh into my box but I'd still like plain old physical access, particularly while I get things like tailscale, DNS, and a reverse proxy setup.
Id also like to make sure my work PC and home PC are completely segregated for legal reasons, but I plan to to ssh into it from a different laptop anyway.
Use WSL on the laptop for ssh, that's actually a VM. VM separation should work correctly, or we have a much bigger problem. Just reset WSL, everything should be wiped related to the ssh sessions. Work IT would maybe allow that.
Note that some issue devices have VT-x disabled and the bios locked down by Corp IT for one reason or another, so a VM may not actually be possible from the work issue device here.