pyramid currently doesnt support running a private grasp service
DanConwayDev
freedom tech developer and creator of ngit, https://gitworkshop.dev and https://metadata.nostr.com
Nice!
https://blossom.ditto.pub/a1db480cb5ca201cf5c3b7d22dee9d7…
🎓 ngit v3 and GitWorkshop v4 launch! The biggest release yet brings CI, private repositories, forge-free software releases and much more. Grasp is the powerhouse behind ngit. The launch also includes ngit-grasp v3, the new ngit-ci 0.1 and an entirely new docs site. https://ngit.dev/v3
🎓 ngit v3 and GitWorkshop v4 launch! The biggest release yet brings CI, private repositories, forge-free software releases and much more. Grasp is the powerhouse behind ngit. The launch also includes ngit-grasp v3, the new ngit-ci 0.1 and an entirely new docs site. https://ngit.dev/v3
Yes
I think they have done a good job so far
Thanks npub1qny3tkh0acurz… for the ngit shoutout on npub10uthwp4ddc9w5…. Is this the nicest thing you have ever said about a nostr client name?
https://haven.danconwaydev.com/5c6cec8384862d93723803afe8…
nevent1qgs879mhq6k…
https://haven.danconwaydev.com/5c6cec8384862d93723803afe8…
nevent1qgs879mhq6k…
Wow. Sorry to hear that. Did you have any backup of the issues / replies?
How's the gnostr stuff going?
O. I thought that meant that it is online now but some sort of source fallback may not be yet. What exactly is online now?
I'm not seeing that comment.
This is because a git repository can't be found at the git.gitter.space address listed in the announcement. nprofile1qqsf4qmhn…?
nprofile1qqsf4qmhn… we should have a call sometime to discuss compatible. Would you be up for that? I reached out the other day on telegram.
I'm a bit confused. Are you are saying the extra complexity of having lots of different ways of doing the same thing is OK? And that you made a PR to a project that has only 1 commit posted 2 years ago.
nprofile1qqsf4qmhn… are you worried that supporting so may ways of doing the same thing, adds unnecessary complexity, makes it harder to understand and harder to implement?
Your making some fantastic progress on this and quickly. Can you fix your announcement event so it clones from the `nostr://` URL? Files in repos are loading really fast. Are you SSR them?
O cool. Do you mean until your confident your app won't create noncompliant NIP-34 kinds?
That all makes total sense. Reacting to a repository isn't and shouldn't be the same as following it.
You CTRL-C exited the interactive `ngit init` command before publishing the event. `? repo name (keyboard) > ` is a prompt for the name of the repo, defaulting to 'keyboard'. So press enter to continue.
No! At the risk of duplicating the conversation on the NIP PR npub180cvv07tjdrrg… just opened:
In nevent1qvzqqqqqqyp… I proposed we should add a Git repository 'set' with a default d=starred that acts as a follow list.
but maybe a 'standard' NIP-51 git repository follow list like that PR suggests is better. Would / should clients label this list as starred repositories? I think may git clients will want to inherit the 'starred' concept from github but I there is an overlap with reactions, zaps and a repository follow list.
We should definately add git repositories as a set.
BudaBit is using lists for git repositories so we should also build on their work npub1ehhfg09mr8z34… npub16p8v7varqwjes….
In nevent1qvzqqqqqqyp… I proposed we should add a Git repository 'set' with a default d=starred that acts as a follow list.
but maybe a 'standard' NIP-51 git repository follow list like that PR suggests is better. Would / should clients label this list as starred repositories? I think may git clients will want to inherit the 'starred' concept from github but I there is an overlap with reactions, zaps and a repository follow list.
We should definately add git repositories as a set.
BudaBit is using lists for git repositories so we should also build on their work npub1ehhfg09mr8z34… npub16p8v7varqwjes….
This UX needs to be tightened up. Maybe it should detect that the signed in account is attempting to push to a repo that they have been added to as a mantainer and auto accept the invite (issue an announcement event listing the other maintainers) before completeing the push.
also have a GUI to manage this eg in gitworkshop this would be nice.
also have a GUI to manage this eg in gitworkshop this would be nice.
Is the repository 'keyboard'?nostr:naddr1qvzqqqrhnypzq4eszr4s7slulsjnc2y4s2xnp0mf8xc9vwzw9nrxfr6qp94v4m6wqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsqzrtv4ukymmpwfjqh0ukvh
Your npub is listed as a maintainer but it hasn't issue an announcement event which 'accepts' the invite.
This means you haven't successfully run `ngit init` under this npub. Maybe you ran it again under the other npub thus just updating the announcement? Run `ngit account login` to switch accounts before running `ngit init.
Your npub is listed as a maintainer but it hasn't issue an announcement event which 'accepts' the invite.
This means you haven't successfully run `ngit init` under this npub. Maybe you ran it again under the other npub thus just updating the announcement? Run `ngit account login` to switch accounts before running `ngit init.
I think developers want to set it in one place and have it 'just work' whenever a branch is pushed. We could bundle web hooks / CI/CD config that doesn't live in the git repo into either a new event or the repo announcement. We could potentially encrypt secrets nip44 style to the pubkey of the a selected grasp operator.
Yes but which client? The idea is this you could push from any clients and not every client will support it and not all will have the secret l.
This is brilliant! It requires webhooks though. I've been ruminating on this. A single service should trigger the webhook as if all grasp servers did it, it would be deployed multiple times. A service like this is really simple with minimal compute but may require secrets to be loaded by the maintainer (eg for signing an authorisation like in one scenario in this case). This is the same trade-off you might have with a more elaborate CI/CD runner so why not combine them as one service following the same model. The could be seen as a loosely coupled extension to a grasp service, with a subset of operators offering it. Compute requirements for CI/CD can vary a lot. for things like a webhook is basically 0 so an allowance per pubkey / repo and then payment for more might be appropriate. a freemium model.
Who said what?
I wrote this on Amethyst without all the capitals and tagged in nprofile1qqsqqqqqq…. This bug on one of the most used and best clients illustrates the point nicely. https://cdn.satellite.earth/7104407e5e2494bf41f48d4eb53d7…
nprofile1qqsqqqqqq…, nprofile1qqsvmm558…, nprofile1qqsdqnk0x… and nprofile1qqswgvmv6… are actively working on git nostr tools. nprofile1qqsthdwa5… sometimes too. We don't work on the same tools and all our tools still feel experimental. Maybe this also sums up the nostr ecosystem.
I assume they included a verifiable cryptographic signature inside the envelope
Very good!
These guys are hilarious! How don't not know about them?

