dbx12

If all of those servers are yours (which they likely are, since you get ssh access), you can use one key for all. Using different keys would make one compromised key less problematic. But if someone was able to copy one file of your system, they can copy multiple files.

That resolves keeping track of things as well 😄

Ducking Medium again. No I don’t want an account with you. The article can’t be that interesting.

I would recommend key based authentication for SSH connections. For the normal connection, the key pair is enough, if you want admin (root) access, you would use the command sudo which in turn requires a password. For creating a default admin account: Linux does this for you, it’s called root. You should create a personal user to work with in daily business and add it to the sudoers group (permits using the sudo command)

Since when is hiking in torch light proof of fascism fantasies?

For the maven password, ok maybe. Your ssh private key should require a passphrase.

But now you have the only credential, the REPO_TOKEN in plaintext in your .git/config file. That’s even worse.

Edit: typo

Make them non-admins and make the “difficult dashboard” admin-only. At least that is my way of doing it.