Skip to main content

Git, Mirrors and Nostr

Our code reaches you over four transports — one canonical host we run, three org-owned mirrors — plus a fifth path that needs no forge at all: a clone over Nostr through our GRASP server.

The four transports​

RemoteRoleURL
ForgejoCanonical (self-hosted)git.rugmunch.io/RugMunchMedia
GitHubPush mirror — org-ownedgithub.com/Rug-Munch-Media-LLC
GitLabPush mirror — org-ownedgitlab.com/rug-munch-media-group
CodebergPush mirror — org-ownedcodeberg.org/RugMunchMedia

Forgejo holds 48 repositories, 14 of them public. Commits land there first. The three mirrors are one-way and owned by the same organisation — not by personal accounts. Review happens on Forgejo; a pull request opened on a mirror gets pointed back here.

Push cadence: Forgejo on every commit; mirrors weekly, plus on feature completion.

In a local clone the remote names are origin (Forgejo) and github, gitlab, codeberg.

Clone​

# Forgejo — HTTPS
git clone https://git.rugmunch.io/RugMunchMedia/<repo>.git

# Forgejo — SSH (port 2222)
git clone ssh://git@git.rugmunch.io:2222/RugMunchMedia/<repo>.git

# Mirrors (read the same refs)
git clone https://github.com/Rug-Munch-Media-LLC/<repo>.git
git clone https://gitlab.com/rug-munch-media-group/<repo>.git
git clone https://codeberg.org/RugMunchMedia/<repo>.git

The fifth path: Nostr via GRASP​

Every public repository is announced as a signed Nostr event (NIP-34, kind 30617) and pushed to our GRASP server, which serves git over the Nostr transport. That means a clone needs no forge account, no DNS zone you have to trust, and no host that can quietly swap the history: the announcement is signed, so the record of the repository does not depend on a server answering.

FieldValue
Public key (npub)npub1e97559tn2j6j02shalmn5x6xv5jt8ejlclh6sta8nln0n55whwtszyrqud
GRASP hostgit.cryptorugmunch.com
Relaywss://git.cryptorugmunch.com

Working clone command — substitute any public repository name:

git clone nostr://npub1e97559tn2j6j02shalmn5x6xv5jt8ejlclh6sta8nln0n55whwtszyrqud/git.cryptorugmunch.com/<repo>

Example:

git clone nostr://npub1e97559tn2j6j02shalmn5x6xv5jt8ejlclh6sta8nln0n55whwtszyrqud/git.cryptorugmunch.com/rmi-backend

This is an additional transport, not a replacement. Forgejo stays canonical: same commits, same refs, same repository identifiers.

Verify an announcement yourself​

  1. Open the npub in any Nostr client — njump.me/npub1e97… is one option.
  2. Filter to kind 30617 — repository announcements; everything else is a different event kind.
  3. Compare the repository identifier in the event with the canonical source at git.rugmunch.io/RugMunchMedia/<name>. Same identifier, same repository.

If the announcement and the forge agree, the code you are reading is the code we signed for.

Tooling​

NIP-34 is a spec, not an app. The client we publish with is ngit, a Rust binary that ships a git remote helper:

cargo install ngit # or: nix run github:nostr-org/ngit
ngit account login # import the signer you publish with
ngit --version

Everyday commands: ngit init, ngit repo edit, ngit pr, ngit issue, ngit ci, ngit release, ngit sync.

Notes​

  • Radicle: publication stopped on 2026-09-27. Radicle 1.x transmits private repository content in cleartext and its peer authentication can be impersonated, with the fix deferred to a wire-incompatible 2.0. Publication is permanent and cannot be recalled, so we stopped propagating. A read-only archive browser remains at code.cryptorugmunch.com.
  • Mirrors are not review surfaces. Issues and patches belong on Forgejo.