Skip to content
This repository was archived by the owner on Apr 17, 2026. It is now read-only.
This repository was archived by the owner on Apr 17, 2026. It is now read-only.

Migrate to Nebulus instead of IPFS or use offline ipfs. #25

Closed

Description

@dm3ch

Even self-owned IPFS instance shares information about contained files with other network.

https://nebulus.dev/

In https://discord.com/channels/438038660412342282/791444480628490290/867026354419007509 proposed Nebula to prevent sharing private subnets.

Or consider tuning IPFS to private mode - https://docs.ipfs.io/concepts/privacy/

Activity

  1. dm3ch commented on Aug 19, 2021

    @dm3ch
    ContributorAuthor

    Also research if file pinning needed

  2. changed the title [-]Migrate to Nebula instead of IPFS[/-] [+]Migrate to Nebulus instead of IPFS or use offline ipfs.[/+] on Sep 2, 2021
  3. dm3ch commented on Sep 2, 2021

    @dm3ch
    ContributorAuthor

    #66 should prevent files sharing with whole network.

    But maybe in future it would worth it to rewrite ipfs chart and deploy multiple ipfs nodes at same time as private network.

    For now I don't think it's needed, cause as far as I understood graphprotocol-node only requests ipfs on start (or new subgraph deploy) to download WASM subgraph code, so we don't need IPFS to be HA to make graph indexer HA, I believe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions