rns.recipes

I have started a rngit node.

I have created a group in the node config. Then I have created a repo using rngit create.

Now I try to git clone rns://...

On the client I get the error :

git-remote-rns failed: Fetch failed for batch: Could not fetch refs

And on the rngit node I see the log :

[Error]    Error while fetching refs ['refs/heads/main', 'refs/heads/master'] for <group>/<repo>: fatal: ambiguous argument 'refs/heads/main': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Even the Nomad Network rngit interface reports an error : The ref 'HEAD' does not exist in this repository.

Can anybody tell me what's wrong and what I can do ?
All I did was creating the repo.

I have re-installed my rngit, fresh config, on another node I use rngit create, it says Repository created.

And then I git clone that repository and get the same errors.

Something ain't right with this.

anyone actually using rngit ? Can you give the commands that work for you in order to create and clone a repo ?

Thanks,
Tukan

pelikan: try initialising the repository locally with git init, then add the remote using git remote add <NAME <URL> and push an initial commit to the remote.

rngit is hard-coded to use master as the default branch name. If you're using main (the newer git default), you need to fix it server-side by running this in the repo folder:

git symbolic-ref HEAD refs/heads/main

You need to do this only once, but you need to do it for each repository.

I probably should look it we can make rngit server detect the branch automatically. We have dozens of repositories, and doing this every time we create a new one is tedious.

@Mark maybe worthwhile to document? This is the second time I see this question in a short while.

I agree with bergie. I was coming back to check on my thread and saw this one. I've had limited time to dig into this so far.

bergie wrote:

I probably should look it we can make rngit server detect the branch automatically. We have dozens of repositories, and doing this every time we create a new one is tedious.

rns://adafb3153efd4d96d532568a5208b3b5/reticulum/reticulum branch rngit-default-branch implements this if somebody wants to give it a spin.

This patch doesn't resolve the Nomad pages issue where it tries to browse master by default. It still says my repo lacks a README, and says there's no HEAD when I nagivate to Files. I can still browse by manually selecting 'main'. So no change there, but not sure about the other issues.

Thank you for the attempt, and I'm happy to test iterations. :)

Gwyn wrote:

Thank you for the attempt, and I'm happy to test iterations. :)

There's more work up there now.

That seemed to do the trick!

Interestingly I just tried rns 1.5.7 without your patches, and that seems to resolve the page browsing issue. I think the markdown->micron README commit fixed that.

Gwyn wrote:

Interestingly I just tried rns 1.5.7 without your patches, and that seems to resolve the page browsing issue. I think the markdown->micron README commit fixed that.

Since you ran it with my branch before, it has the HEAD ref correctly set.

Ah, ok.