spinframework / spinframework/spin

Configurable (or additional) plugin directory search paths

Open
#1,870 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
6.5k
Forks
310
Avg merge
1d 20h
Merged PRs (30d)
24

Description

Because Spin Plugin binaries are precompiled binaries with a variety of system dependencies, they may not run as-built-by-Fermyon on all systems - for example spin cloud doesn't run on NixOS because the ELF interpreter and openssl have a different path (see also our GLIBC version issues in the past on ubuntu).

It would be helpful to allow package managers to distribute Spin Plugins to account for this (and also means that plugins can be reliably updated in the same manner as people otherwise manage their systems).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing Spin Plugin discovery and installation entry points; the issue does not name specific files or tests. Compare the current behavior with package-manager needs described for NixOS and other systems, then define how additional plugin directories would be configured and how successful discovery should be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.