Skip to content

Add Documentation for non-js plugins #11

@clevinson

Description

@clevinson

This plugin provides capabilities to run ssb-plugins as a separate process, but doesn't explain what the API / interface looks like when writing a non js based plugin.

We should add documentation / examples of how this should look. I see the "go-example" but it's not clear to me exactly what that is for, and what the interface requirements of a non-js ssb plugin actually are.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions