feat(ipos): filebase IPFS worker

[hassnian]

Context

add new ipos worker

envs

bucket: https://docs.filebase.com/getting-started/ipfs-getting-started-guide#how-to-create-an-ipfs-bucket
s3: https://docs.filebase.com/getting-started/s3-api-getting-started-guide#access-keys

 // S3
  S3_ACCESS_KEY_ID: string
  S3_SECRET_ACCESS_KEY: string //  secret env

  // Filebase
  FILEBASE_BUCKET_NAME: string 

Ref

• Closes R2(IPFS) worker #304
• References kodadot/<indexer/worker>#<issue_number>

PR Type

• Bugfix
• Feature
• Refactoring
• Chore

Screenshots

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@cloudflare/[email protected]	None	0	3.7 MB	wrangler-publisher
npm/[email protected]	environment, filesystem, network, shell	0	97.2 MB	aws-sdk-bot
npm/[email protected]	None	0	897 kB	yusukebe
npm/[email protected]	None	0	717 kB	fabian-hiller

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[hassnian]

core packages of the propposed stack are not yet compatible with cloudlflare worker's environment

do we change env or go with another alternative cc @vikiival @preschian

#304

mainly

• https://www.npmjs.com/package/@libp2p/tcp

ref:

• https://community.cloudflare.com/t/how-to-make-node-built-in-modules-work/486465
• https://community.cloudflare.com/t/wrangler-polyfill-nodejs-events-not-working/638259?__cf_chl_rt_tk=tTvo5V2L0F7kT1rghwvy3IqoT3WZKPqqPDPqYAsVR3s-1720863852-0.0.1.1-6356
• net module

[vikiival]

Hey,
Thanks for taking it.

We will use filebase.
I will make new issue for that

[vikiival]

you can use wait until so it's non blocking op

[hassnian]

fixed

[hassnian]

@vikiival @preschian pls create a new worker called ipos and update wrangler.toml , so we can test this out

thanks

[vikiival]

@SocketSecurity ignore [email protected]

[vikiival]

Tested, works as charm

[vikiival]

@SocketSecurity ignore npm/[email protected]