ipfs/kubo

separate ipfs mount into its own separate binary

Open

#2,148 建立於 2016年1月2日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
exp/experthelp wanted

描述

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.

貢獻者指南

技術棧
go
領域
clitooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingIPFS architectureCLI tool design
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
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.
separate ipfs mount into its own separate binary · ipfs/kubo#2148 | Good First Issue