Skip to main content
Tapedrive works as a Git transport. Once the git-remote-tape helper is on your PATH, ordinary Git commands understand tape:// addresses:
The helper is invoked by Git automatically. You keep using git clone, git fetch, git pull, and git push; there is no separate Tapedrive Git command to learn.
The installer includes git-remote-tape; see the installation page for the command and supported platforms.

​
Push a repository

For Tapenet, complete the wallet and funding setup before creating a tape. Keep those connection settings in the terminal you use for Git. Create a tape, add it as a remote, and push the branch:
The helper finds the tape keypair created by the CLI under ~/.tape/cassettes/. Only the tape owner can push. Anyone with the tape address can clone without a wallet or an account. Git uses the same RPC as the CLI: Tapedrive’s at https://devnet.tape.network, then Solana’s public devnet, unless TAPE_RPC_URL sets another. To read through Tapenet’s public gateway, set its URL:
For a local deployment, use your own gateway’s URL. Gateway reads are useful on restricted networks and avoid making Git contact storage nodes directly. The helper verifies returned data before handing it to Git.

​
Storage model and privacy

Each push writes a Git packfile as a content-addressed track. Repository refs live in a named object that each push replaces. Storage is append-only, so sensitive data cannot be made secret by removing it in a later commit. Tapenet repositories are publicly readable to anyone with their address, and the Git helper does not yet encrypt private repositories. Do not push credentials or other secrets. The complete Git example explains the wire layout and current performance characteristics.