tauri-apps/gipfs

Git ops with IPFS

gipfs's Issues

Mission Statement and Next Steps

When the internet faces so-called "global outages", what is really happening is that some critical centralised pipe gets clogged, and dozens of services go down. We see this with cloudflare, github, npm and everyone else in between. There is zero reason why we should suffer because some "customer changed a valid setting" and thereby crashed everything.

To this end, we are working on first and foremost securing our corner of the ecosystem by providing git over ipfs in such a way that anyone anywhere can work on their own projects without needing to use GITHUB or GITLAB.

At first we will secure all of the tauri-apps org's git repositories, but later we will work toward providing and maintaining a complete up to date, versioned, IPFS-based git source for all tauri dependencies (direct and transitive, rust or node).

Then we will provide tooling by which the IPFS sources can be stored locally and ingested by cargo and npm/yarn.

Want to help? Stop by the Tauri Discord server or start hacking!!!

Plan

1. Bridge IPFS
   • git objects to DAG nodes
2. Mirror git repo to IPFS
3. Parse Cargo.toml / package.json from ALL dependencies in all projects
4. cli / lambda

FUTURE

cargo-ipfs install / inpm install
- .cargo-ipfs config file

Name

• find a better one