ipfs/kubo

separate ipfs mount into its own separate binary

Open

#2,148 opened on Jan 2, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
exp/experthelp wanted

Description

It might be nice to have ipfs-mount be a separate binary called through the same mechanism as ipfs update. I don't think we will hit any performance issues with all I/O being done through http rpc, but it might be worth the effort to separate out that code from the rest of the daemon.

Contributor guide

Tech stack
go
Domain
clitooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingIPFS architectureCLI tool design
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the existing mount implementation in the repository. Look for files related to mounting (likely under core/commands or cmd/). Study the pattern used for other separate binaries like 'ipfs update' to understand the mechanism. Propose a design for extracting the mount functionality into a standalone binary that communicates via HTTP RPC.