Skip to content

[LAB-337] Dedicated private IPFS node#567

Merged
alabdao merged 1 commit intomainfrom
ops/lab-337-dedicated-ipfs
Aug 8, 2023
Merged

[LAB-337] Dedicated private IPFS node#567
alabdao merged 1 commit intomainfrom
ops/lab-337-dedicated-ipfs

Conversation

@alabdao
Copy link
Copy Markdown
Contributor

@alabdao alabdao commented Aug 3, 2023

These changes now create and setup a dedicated
IPFS node where both requester and compute now connect.

Also using private_ipfs=true option you can make your
IPFS deployment be private. Currently the swarm key for
private IPFS is randomly generated at bootstrap time.
Next step would be to have this key getting fetched from
AWS SSM parameter store likely.

@linear
Copy link
Copy Markdown

linear bot commented Aug 3, 2023

LAB-337 Dedicated IPFS node

Setup dedicated IPFS node and configure Bacalhau to connect to it.

@vercel
Copy link
Copy Markdown

vercel bot commented Aug 3, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 8, 2023 2:44pm

Copy link
Copy Markdown
Contributor

@hevans66 hevans66 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way things are forwarding to IPFS is clever.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be Provision IPFS

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It took me a bit to wrap my head around how this is working. Its probably worth putting a comment in here that we are forwarding traffic through to the IPFS node for this port only because the cli requires pinning certain files in IPFS. It seems like the thing we might forget and will confuse us later.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will do!

These changes now create and setup a dedicated
IPFS node where both requester and compute now connect.

Also using `private_ipfs=true` option you can make your
IPFS deployment be private. Currently the swarm key for
private IPFS is randomly generated at bootstrap time.
Next step would be to have this key getting fetched from
AWS SSM parameter store likely.
@alabdao alabdao force-pushed the ops/lab-337-dedicated-ipfs branch from e5a24b0 to daa1fac Compare August 8, 2023 14:43
@alabdao alabdao merged commit 6bd0fe7 into main Aug 8, 2023
@alabdao alabdao deleted the ops/lab-337-dedicated-ipfs branch August 8, 2023 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants