cheatsheet_admin: launcher-editor, its checkout, and what publishing to gitea needs

This commit is contained in:
lemke_h committed 2026-10-16 11:18:31 +02:00
1 parent dac7de43c1
commit 4104fdb166
1 file changed
+23
+23
View File
@@ -24,6 +24,29 @@ If `~/network_drives/home` is a plain directory instead of a link, something wro
| `gopass_bernina_setup` | One-shot onboarding for a human PSI account joining the gopass store |
| `gopass_bernina_service_setup` | One-shot setup: give a service account (e.g. `gac-bernina`) access to the gopass store |
## Launcher editor
| Command | Description |
|---|---|
| `launcher-editor` | Edit the Bernina launcher in your own copy (`~/launcher_config`), preview it (F5) and publish it live; `--live` views the deployed one read-only. On `gac-*` accounts it first asks for your user name and runs as you (`become`, password in a terminal) |
- The app is a checkout of `github.com/swissfel/launcher_editor` in
`/sf/bernina/applications/launcher_editor`, run without installing
(bpy312 Python). Update it with
`git -C /sf/bernina/applications/launcher_editor pull`.
- Publish pushes to `gitea.psi.ch:autodeploy_config/sf_bernina_launcher`,
which deploys to `/sf/bernina/config/launcher`. That needs, once per
person:
1. a gitea.psi.ch account (log in there once with PSI SSO),
2. your SSH key added at gitea.psi.ch → Settings → SSH/GPG Keys (same
as step 3a of [rhel9_onboarding.md](rhel9_onboarding.md)),
3. Write access on `autodeploy_config/sf_bernina_launcher`; ask the
admin (Henrik Lemke).
Check with `ssh -T git@gitea.psi.ch` (should greet you by name). On the
consoles `~/.ssh/id_ed25519` links into `~/network_drives`, so if it
says `Permission denied (publickey)`, run `setup-network-drives` first.
This is a hand-picked subset of the full script index (the "Scripts in
this directory" section of the main sheet still lists every one of
these too, alongside everything else) — pulled out here specifically