this post was submitted on 09 Jul 2025
20 points (95.5% liked)

Selfhosted

60707 readers
241 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I'm just using the Cosmic Terminal that's part of the Pop!_OS Cosmic Alpha, but I ran into similar issues with Gnome terminal and even with Termius.

Scenario: I'm currently working on leveraging a VPS to act as the gateway to my homelab so I have one ssh session to Unraid server and one to VPS. One in each tab. Obviously the name shows up as what the username@servername is called in each tab. But I keep getting tripped up and sometimes try to do something from the wrong machine. Once I even failed to realize that the ssh session to one of them cut out and I was back on my desktop and took me an embarrassingly long time to realize why stuff was failing.

So what are y'all using to keep that organized in your work flow? Separate terminal windows instead of tabs? Some shell customizations to make them look different than one another? Or just so ingrained in your brain that you never have this problem?

EDIT: Thanks, everyone! Sounds like a terminal multiplexer is the ticket for me.

all 16 comments
sorted by: hot top controversial new old
[–] neidu3@sh.itjust.works 9 points 1 year ago* (last edited 1 year ago) (1 children)

bash setup/config/PS1 is your friend here. I frequently find myself with a myriad of terminals between a bunch of usernames and servers at work, and setting up a proper prompt is key to help you keep track.

My bashrc makes my prompt look like this:

username@hostname:/absolute/path
$ inputgoeshere

... with color coding, of course. Yes, I use a multiline prompt. I somehow never saw that before using ParrotSec despite being a bash user for 25 years. I modified the ParrotSec default to suit my needs better, and I like it:

  • Obvious which user I am.
  • Obvious which host I'm on.
  • Obvious which path I'm in.
  • It's easy to copy and paste a complete source/destination for pasting into, for example, an rsync comman

I pasted my PS1 config here: https://pastebin.com/ZcYwabfB

Stick that line near the bottom of your ~/.bashrc file if you want to try it out.

[–] Father_Redbeard@lemmy.ml 2 points 1 year ago

Hey that's super helpful, thank you. Definitely going to try this out.

[–] eksb@programming.dev 8 points 1 year ago

I use tmux or screen, and set the status bar in different remotes to different colors.

[–] SheeEttin@lemmy.zip 7 points 1 year ago

Color coding

[–] irmadlad@lemmy.world 3 points 1 year ago

If I'm on WIndows, I use MobaXterm. If I'm on Linux, I use tmux.

[–] dgdft@lemmy.world 3 points 1 year ago (1 children)

You’ll get used to it eventually, but you can e.g. tweak your PS1 to an all-caps hostname, or use a custom tmux layout with dedicated panes for each box you connect to.

[–] IsoKiero@sopuli.xyz 3 points 1 year ago

You’ll get used to it eventually

I've been earning my living mostly with connecting to remote systems via ssh (and other means) for quite a few years and I still occasionally mess up and enter commands on a wrong terminal. Less now than I used to, but it still happens. The trick is to learn youself to pause for a second and confirm the target for any potentially destructive or otherwise harmful command, no matter if it's locally or to some server other side of the world.

[–] illusionist@lemmy.zip 2 points 1 year ago
[–] e0qdk@reddthat.com 2 points 1 year ago (1 children)

I (manually) set the background color of my terminals depending on the machine I connect to. I currently have profiles for red, green, blue, and black backgrounds with black as my default. I usually use red for ones I want to be especially careful of.

[–] Father_Redbeard@lemmy.ml 2 points 1 year ago (1 children)

That's a great idea. Do you have it persist between sessions? Like one server #1 it's always green?

[–] e0qdk@reddthat.com 1 points 1 year ago

I just right click on the terminal to change the profile to whatever I feel like it should be in the moment (usually red). I do it by reflex, basically. I never felt the need to try to set up automation for different servers, but I expect there's probably a way to do that if you really wanted to.

[–] HelloRoot@lemy.lol 2 points 1 year ago (1 children)

I made it so that the ps1 on my servers shows the servername@[server IP]