47
Recommend a KVM or Switch
(self.selfhosted)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Sep 2024
47 points (100.0% liked)
Selfhosted
40645 readers
136 users here now
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!
founded 2 years ago
MODERATORS
One of them is a laptop, why ssh to the server isn't an option? Set up tmux on the server so it always connects to the same session, so you can just continue where you left last time. If you need desktop support, rdp in gnome works really well.
E.g if you connect with this command, and tmux is installed on the server, it will start a new session named "main". If a session with that name exists it will connect to that:
ssh -t pi@192.168.1.2 tmux new-session -A -s mainAdd something to .bashrc on the server to always do the same if you work on that phisically:
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.