From 3c49fff91bd94b1c3e649ed4fabb7569fa36b34a Mon Sep 17 00:00:00 2001 From: druid520 Date: Sat, 15 Aug 2026 18:10:20 +0000 Subject: git.html + homepage/git links --- git.html | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 git.html (limited to 'git.html') diff --git a/git.html b/git.html new file mode 100644 index 0000000..7a2033b --- /dev/null +++ b/git.html @@ -0,0 +1,42 @@ + + + + + + 0druid.cc - git + + + +

git.0druid.cc

homepage. git.

this is my git forge. its invite only, accounts are made by me, and everything is public to clone but only people with accounts can push. if you want an account, email me with your ssh pubkey.

browsing happens at git.0druid.cc, with the usual stuff: commits, tree, refs, diffs n such.

clone over https (read only):

git clone https://git.0druid.cc/druid520/site.git

clone and push over ssh (accounts only):

git clone git:druid520/site.git

accounts get ssh commands too:

ssh git mk <repo>
+ssh git desc <repo> "description"
+ssh git perms <repo> +WRITERS <user>
+ssh git ls

put this in ~/.ssh/config:

Host serv
+    HostName 0druid.cc
+    User root
+    Port 3447
+    IdentityFile ~/.ssh/serv
+    ProxyCommand sh -c "nc -z -w 1 %h 47910; exec nc %h %p"
+
+Host git
+    HostName git.0druid.cc
+    User git
+    Port 3447
+    IdentityFile ~/.ssh/druid
+    ProxyCommand sh -c "nc -z -w 1 %h 47910; exec nc %h %p"

the serv host is the server itself, it knocks a secret port before ssh answers so scanners see nothing. the git host is the same machine, same deal.

profiles: push a repo named the same as your username (like druid520/druid520) with a profile.png and a readme.djot in it, first line like this:

{desc="hi" location="somewhere" work="stuff"}

and the rest of the file is your page.

+ + -- cgit 1.4.1