sls/hla_framework_bd
0
1
Fork 0
Code Issues 23 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

docs: setup vserv machine

Browse Source
This commit is contained in:
Benjamin Labrecque
2026-08-25 11:59:10 +02:00
parent 5b8a3aa865
commit 48ce2db228
1 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/developer/cicd_runner.md
+25
View File
@@ -184,3 +184,28 @@ The gitea actions run as user `svcusr-sls2hla`
### #TODO: this is a temporary workaround
I created an ssh key on `sls-vserv-bd-hla01-dev` (where the runner runs), and added the public key to my
gitea profile ssh keys. That way the `svcusr` can clone the repos I can clone.
## Setup `sls-vserv-bd-01-dev`
On `sls-vserv-bd-hla01-dev`
```
sudo su - svcusr-sls2hla
cat ~/.ssh/id_ed25519.pub
```
If it does not exist yet:
```
sudo su - svcusr-sls2hla
ssh-keygen -t ed25519 -N "" -C "svcusr-sls2hla@sls-vserv-bd-hla01-dev" -f ~/.ssh/id_ed25519
cat ~/.ssh/id_ed25519.pub
```
```
ssh sls-vserv-bd-01-dev # lands as your own user
sudo install -d -m 700 -o svcusr-sls2hla -g unx-nogroup /home/svcusr-sls2hla /home/svcusr-sls2hla/.ssh
echo '<paste the pubkey>' | sudo tee /home/svcusr-sls2hla/.ssh/authorized_keys
sudo chown svcusr-sls2hla:unx-nogroup /home/svcusr-sls2hla/.ssh/authorized_keys
sudo chmod 600 /home/svcusr-sls2hla/.ssh/authorized_keys
```