Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Configuration for Connecting to IPFS Private Network (pnet) #398

Merged
merged 8 commits into from
Mar 1, 2025

Conversation

HX2012
Copy link

@HX2012 HX2012 commented Feb 28, 2025

This pull request aims to add functionality to the existing codebase that enables the configuration of connections to an IPFS private network (pnet). By implementing this feature, users will have the ability to interact with a private and potentially more secure IPFS network environment, which is crucial for applications that require data privacy, restricted access, or operation within a closed - group infrastructure.

Copy link
Owner

@dariusc93 dariusc93 left a comment

Choose a reason for hiding this comment

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

Thanks for the PR. Could you enable the pnet feature in the Cargo.toml?

Cargo.toml Outdated
@@ -134,6 +134,7 @@ tracing-futures = { workspace = true }
unsigned-varint.workspace = true
web-time.workspace = true
zeroize.workspace = true
libp2p = { workspace = true, features = ["pnet"] }
Copy link
Owner

Choose a reason for hiding this comment

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

Can we add this feature on libp2p under [target.'cfg(not(target_arch = "wasm32"))'.dependencies]? I think we could also add it under the dependencies targeting wasm32, no? I never tried pnet on wasm targets so I wouldnt know for sure so we could probably exclude it from that section for now.

What are your thoughts on that?

Copy link
Author

Choose a reason for hiding this comment

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

You're right. We can add the feature under [target.'cfg(not(target_arch = "wasm32"))'.dependencies] first. Since we're uncertain about its performance on wasm32 targets, excluding it from that section for now is a practical approach.

Copy link
Owner

@dariusc93 dariusc93 left a comment

Choose a reason for hiding this comment

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

Thanks! Lets gate pnet stuff since we wont be compiling it on wasm32

Co-authored-by: Darius Clark <dariusc93@users.noreply.github.com>
@HX2012
Copy link
Author

HX2012 commented Mar 1, 2025

I'm new to this. Thanks a ton for the guidance!

Copy link
Owner

@dariusc93 dariusc93 left a comment

Choose a reason for hiding this comment

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

Thanks!

@dariusc93 dariusc93 merged commit 41facf0 into dariusc93:libp2p-next Mar 1, 2025
2 checks passed
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