- commit
- f399c8544a22d6b572b411ee643b3d7ad0a4c7a9
- parent
- d37c16a38bee59506d906fd0a8fe4afee467976b
- Author
- Tobias Bengfort <tobias.bengfort@posteo.de>
- Date
- 2023-08-07 18:46
README: update examples
Diffstat
M | README.md | 6 | +++--- |
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
@@ -30,8 +30,8 @@ Then setup access control: 30 30 31 31 ``` 32 32 [private]33 -1 ssh = admin dilbert34 -1 post-update = git --work-tree=/var/www/example checkout -f master-1 33 ssh = admin hobbs -1 34 post-update = git --work-tree=/var/www/example checkout -f main 35 35 36 36 [example] 37 37 desc = my shiny new project @@ -51,7 +51,7 @@ The authorized keys file should look roughly like this: 51 51 52 52 ``` 53 53 command="/usr/lib/stagit/shell admin",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa … admin@example.com54 -1 command="/usr/lib/stagit/shell dilbert",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa … dilbert@example.com-1 54 command="/usr/lib/stagit/shell hobbs",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa … hobbs@example.com 55 55 ``` 56 56 57 57 It is mostly a regular authorized keys file with some restrictions. Most