fix: make sure folks know that adding a password to a ssh key will cause CI/CD to fail
All checks were successful
Build / build (push) Successful in 14s
Build / deploy (push) Successful in 10s

This commit is contained in:
silver 2025-02-09 21:21:32 +00:00
parent 347c979b35
commit 96822e7b2f
Signed by: silver
GPG key ID: 36F93D61BAD3FD7D

View file

@ -4,7 +4,7 @@ To be able to gain remote access to the Skynet.
``$USERNAME`` Refers to your Skynet username, for example I would replace ``$USERNAME`` with ``silver``
## Create Key
## Prep
First we set up the ssh folder and create a skynet folder within it for neatness
```bash
@ -12,9 +12,12 @@ mkdir -f -p ~/.ssh/skynet
cd ~/.ssh/skynet
```
## Create Key
Now we will create the ssh key itself.
Location: ``$USERNAME``, your skynet username.
Password: Press Enter twice for no password on the key.
**Password: Press Enter twice for no password on the key.**
If you are creating this key for a CI/CD pipeline (``user_deploy*``) then adding a password will cause it to fail.
```bash
ssh-keygen -t ed25519 -C "<comment>"