ipfs/kubo

System-wide plugins

Open

#4238 opened on Sep 17, 2017

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedstatus/deferred

Description

It would be useful to have system-wide plugin directory, like /usr/lib/ipfs/plugins. This would allow distributions to package IPFS plugins.

This could be only enabled when building ipfs with some flag, such as PLUGIN_PATH=/usr/lib/ipfs/plugins make build.

Contributor guide

Tech stack
goshell
Domain
backendbuild system
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-3 hours
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.
mostly clear
Prerequisites
Basic Go knowledgeUnderstanding of IPFS plugin systemFamiliarity with Makefile build flags
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests a system wide plugin directory (e.g., /usr/lib/ipfs/plugins) controlled by a build flag like PLUGIN PATH. To implement, investigate the current plugin loading mechanism in the kubo codebase, likely in files related to plugin initialization (e.g., core/commands/plugin.go or similar). Determine where plugin directories are currently configured and how to add an additional system wide path. The feature should only be enabled when built with a specific flag, so the Makefile and build system need modification. Consider discussing with maintainers about default paths and distribution packaging.