GN. ๐ŸŒ GitRepublic Web has already come a long way. 1. Spent two whole days, refactoring, but I still haven't managed to stop it from spawning zombie processes during polling. I'll look at it, again, next time and rehost the repo when I get it fixed. 2. Implemented release events for the tags, that include the zip-download URL. 3. Local cloning to localhost/dev and online editing/adding/saving of all files works. 4. You can add a Markdown or Asciidoc documentation event (30818 default), or just stick to the ReadMe. 5. Branch management for empty repos was very hard and I am now git-traumatized, but it works. I suffer, so that you don't have to. 6. Issues, PRs and patches implemented, including code highlights and comments. 7. Changed access management to be more granular. Now have public, unlisted, restricted, private. (Private saves all events to the repo, rather than publishing them to relays. Share the events with other git repos and stay off the Nostrnet.) 8. Kind 11 discussion thread under very repo. Lots more bug-fixing and testing to go, but all MVP features are implemented and proven. Project management and Kanbanstr not until v.0.2.0 I need to work on other stuff, like the data imports and aitherboard #spells and the mysterious something something from our mysterious boss @MichaelJ, so I will get back to this repo next week. image #GitRepublic #gnostr

Replies (1)

Don't forget that the CLI is separate and allows you to AUTH onto the git server and *sign the commits with your Nostr key*. Also remember that *you actually only need normal Nostr relays and the normal git CLI to do any of this stuff*. There is no extra server or separate data store. The clients are just for convenience and UX.
โ†‘