Make an example app using Fission's webnative to save SQLite to IPFS

[bmann]

Jason S wrote in the Filecoin #arg Slack channel:

I was setting down to build an interface that would allow me to query SQLite databases over IPFS without loading the entire file on the client. Fortunately the IPFS gateway supports HTTP ranges so this pre-built solution worked great for me.

https://github.com/phiresky/sql.js-httpvfs

Further plan is to build on top of this library the ability to perform updates to the database and save a new backup on the IPFS network

We'd love to support this! We want to see a demo app that implements saving to IPFS.

The example app should:

• use Fission's webnative library including auth system to save to a user's public or private file system on IPFS
• have a well written README explaining how to run locally
• have a sample app deployed to Fission's publishing stack (ideally with GH Actions)
• have source code available via git under an open license

Instead of the linked repo in the quote, this might also be an excuse to extend the absurd-sql example project with webnative support.

You might also make use of Fission's WNFS versioning features to do something interesting.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 10.0001 FIL (656.71 USD @ $65.67/FIL) attached to it as part of the fission-suite fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  • Want to chip in? Add your own contribution here.
  • Questions? Checkout Gitcoin Help or the Gitcoin's Discord
  • $7,189,525.09 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Workers have applied to start work.

These users each claimed they can complete the work by 265 years from now. Please review their action plans below:

1) sksb2180 has applied to start work _(Funders only: approve worker | reject worker)_.

Fission webnative includes things needed to do this task. I'll start it asap after confirmation.

Learn more on the Gitcoin Issue Details page.

[gitcoinbot]

@jtsmedley Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[bmann]

Sorry @jtsmedley, I snoozed this, don't know if I can make this not happen.

[jtsmedley]

That's a bummer. I'm still going to build the tooling out and may use fission for key transfers but the data access layer seems like it may be better handled separately right now and then my tool can just sync the public CID of the encrypted database into your public store. That way it's compatible with Fission but also capable of being standalone with your own estuary.

[bmann]

Just to be clear! Totally going to bounty you on this, just that I don't know if I can do anything about this auto-bot :)

Yeah, there's a dag-add so that it can be just added that way. No rush!