Damus

Recent Notes

DanConwayDev · 1d
https://gitworkshop.dev/danconwaydev.com/ngit/tree/main/CHANGELOG.md
DanConwayDev · 1d
I should also tease a grasp implementation ive been working on that live at relay.ngit.dev.
Silberengel · 5d
Nevermind.
Silberengel · 6d
Yes, but if I look at actual announcements, they only contain the GRASP addresses. How does the GRASP server know where to get the repo from, if I only tell it to look at itself? Is there some second ...
DanConwayDev profile picture
The repository state is stored in the repository state event. The maintainer publishes a new /updated state event and pushes the associated new git data to the grasp servers. The ngit git plugin is convenient for this all behind a `nostr://` remote. Nak also has support (run `nak git --help` and some other tools handle this themselves though eg Shakespeare.
1
Silberengel · 5d
I need to know the event for pushing the new git data to the grasp servers, so that I can also publish that kind. I can't find that event description in the docs.
Silberengel · 6d
Yes, but if I look at actual announcements, they only contain the GRASP addresses. How does the GRASP server know where to get the repo from, if I only tell it to look at itself? Is there some second announcement event, that only goes to the GRASP servers? ``` { "content": "", "created_at": 176...
Silberengel · 1w
Okay, I got that working, for viewing. And I got repo announcements and Grasp list events done, but I can't figure out how the Grasp server knows where the clones are. I looked here, but that didn't really say anything. https://ngit.dev/grasp/
Awiteb · 1w
Why?
Nash · 1w
Thanks for sharing that! I can see the comment when logged in - the visibility seems to work as expected. Interesting discussion point!
Travis Knot · 1w
Yes, it does. What is the biggest problem you're facing with ngit right now? https://image.nostr.build/61ec486c30daf66ef9d0ea8cf4e1d322ec2f280fdf21841bc0f25a5ad0a42066.png
Justin Moon · 1w
Thanks!