possible bug: bare git without packed-refs file wouldn't show up in the scan result

[darkclip]

if you init a bare repo in the scan path, it won't create "packed-refs" file by default, in this case, the program wouldn't recognize it as a repo. you have to use "git pack-refs --all" command to create the file for the repo to be recognized by rgit.

[stappersg]

Nice.

I'm now testing

--- a/server_side/rgitsss
+++ b/server_side/rgitsss
@@ -111,6 +111,8 @@ rgitsss_init() {
     COMMAND="${COMMAND}git init --bare --initial-branch=main ${BASE}"
     su ${ACCOUNT} --shell=/usr/bin/bash \
         --command="${COMMAND}"
+    su ${ACCOUNT} --shell=/usr/bin/bash \
+        --command="cd ${DIR}/${BASE} && git pack-refs --all"
 }
 
 rgitsss_describe() {

[w4]

Interesting @darkclip. I wonder if there's any other identifying file in the repo that can be used instead. Maybe git-daemon-export-ok which is the file that needs to be created to allows clones?

[stappersg]

The git pack-refs --all does provide what rgit seams to need for displaying.

For "allow to be cloned" has script rgitsss subcommand publish, which does touch git-daemon-export-ok.

[darkclip]

@w4 I think it doesn't matter that much what kind of identifier to be used, as long as you give it a proper documentation.

[stappersg]

On Tue, Jan 23, 2024 at 08:04:06AM -0800, DC wrote: Closed #50 as completed.

And thanks for the reminder on #29

Groeten Geert Stappers -- Silence is hard to parse