simple git-shell-commands to interact with git over ssh
Find a file
2024-02-08 21:49:29 +01:00
descr feat: pushing existing commands 2024-01-12 09:46:11 +01:00
downstream feat: downstream command maybe? 2024-02-08 21:48:38 +01:00
fetch-mirrors fix: properly recur in subdirs, handle paths 2024-02-08 15:43:46 +01:00
group fix: messages 2024-02-08 20:20:04 +01:00
head fix: also set cgit defbranch config 2024-02-08 19:47:41 +01:00
help fix: merge branch 'dev' into dev 2024-02-08 21:49:29 +01:00
hide feat: use cgit ignore instead of custom ln hack 2024-02-08 19:47:00 +01:00
log feat: pushing existing commands 2024-01-12 09:46:11 +01:00
ls feat: removed public, ls marks hidden repos 2024-02-08 19:47:16 +01:00
mirror feat: pushing existing commands 2024-01-12 09:46:11 +01:00
new fix: new repos are hidden by default 2024-02-08 19:47:28 +01:00
owner fix: messages 2024-02-08 20:20:04 +01:00
page feat: pushing existing commands 2024-01-12 09:46:11 +01:00
pic fix: messages 2024-02-08 20:20:04 +01:00
README.md docs: added a bad readme 2024-01-12 09:53:15 +01:00
show feat: use cgit ignore instead of custom ln hack 2024-02-08 19:47:00 +01:00
tree feat: pushing existing commands 2024-01-12 09:46:11 +01:00
update-time feat: update-time shows the times, also fix 2024-02-08 21:03:25 +01:00
upstream feat: pushing existing commands 2024-01-12 09:46:11 +01:00

Git Shell Commands

did you know that you can push and pull to your repositories over ssh? $ git clone <user>@<host>:<path>

and voila! self hosted repositories

but that's kind of crude: interacting with such repo requires to ssh in

git shell

git ships with a super simple shell (more here)

creating a git user and dropping these command inside git-shell-commands (must live in git user's home) will allow to run them after ssh-ing: $ ssh git@<host>