aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Jonas Gunz <himself@jonasgunz.de> 2020-07-20 04:13:18 +0200
committerGravatar Jonas Gunz <himself@jonasgunz.de> 2020-07-20 04:13:18 +0200
commitb02ba8ab80f5323250c629fbf55af9b036196529 (patch)
tree70afb993cf533f55f618f2ba0c68b6258f10276b
parenta96b78c44a139bfd3ebbb5f46f7312c92163866f (diff)
downloadreposync-b02ba8ab80f5323250c629fbf55af9b036196529.tar.gz
readme
-rw-r--r--Readme.md24
1 files changed, 15 insertions, 9 deletions
diff --git a/Readme.md b/Readme.md
index 999d30a..64f5c5b 100644
--- a/Readme.md
+++ b/Readme.md
@@ -4,15 +4,21 @@ Script for juggling git repos
## gitwrapper.sh
-Its main purpose is to create a new empty repo if a push to a non-existent one is requested.
-It is intended to be used with `command=` option in `.ssh/authorized_keys`.
-As a side effect, it also implements a crude access control via SSH keys.
-The first argument is the folder this specific key is allowed to push to.
-
-If the command invoked by the ssh client is not `git upload-pack`, it is executed without further checking,
-if none is supplied bash starts in interactive mode.
-This would allow anyone to easily override the push restrictions,
-so they should be seen as a fuck-up-preventer, not a security measure.
+gitwrapper.sh automatically creates repositories if they are pushed for the first time.
+If a non-existent repo is pulled, an empty one is sent instead.
+
+This allows for easy creation of new repos by just cloning any name, creating a first commit,
+and then pushing.git@git:jonas/toybox.git
+
+`gitwrapper.sh OPTIONS` is set as a command in `.ssh/authorized_keys`
+
+#### Options
+
+ gitwrapper.sh OPTIONS
+ -r <DIR> Allow pull from DIR
+ -w <DIR> Allow push to DIR
+ -a <DIR> Allow push/pull from/to DIR
+ -i Allow inetractive Login
## reposync.sh