ipfs/kubo

wishlist: way to ensure ipfs daemon is running

Open

#862 opened on 2015年3月6日

GitHub で見る
 (6 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedtopic/commandstopic/daemon + init

説明

When building things on top of the ipfs cli, such as the git-annex integration, it would be useful to have a command that makes sure the daemon is running, starting it up if not, and exits 0 once the daemon is running. This way if the user forgot to start the daemon, ipfs can still be used by the thing built on top of it.

It would be especially nice if the command blocked until the daemon had gotten bootstrapped enough to the DHT that requests for objects were likely to start to succeed.

コントリビューターガイド

技術スタック
go
領域
cliinfrastructure
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
Go programmingBasic understanding of IPFS daemon
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
Investigate the current IPFS CLI's daemon handling, focusing on the `ipfs daemon` command implementation in cmd/ipfs/daemon.go. Look for existing checks for daemon status in commands like `ipfs id` or `ipfs swarm peers`. Consider implementing a new command or extending existing ones to check if the daemon is running and to start it if needed. The challenge includes determining when the daemon is sufficiently bootstrapped. Review linked issues in comments for prior discussions.