npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ssbd

v0.0.3

Published

ssb (secure scuttlebutt) p2p daemon

Downloads

5

Readme

ssbd

ssb (secure scuttlebutt) p2p daemon

installation

npm install ssbd

usage

const sbot = ssbd(options)

config

See https://github.com/ssbc/ssb-config#configuration for documentation on ssb config.

appname

ssb uses rc under the hood to search for config in the usual os specific places and also merges user supplied config. The default ssb appname is ssb with application data at ~/.ssb. Set the appname if you want to override the default path.

ssbd sets the appname like so:

const appname = process.env.ssb_appname || options.appname || 'ssb'

If you don't set the appname it will fallback to ssb.

You may set ssb_appname in your shell to override the appname. Useful for testing or deployment controlled by environment variables.

export ssb_appname=whatever

To set a default appame used by your application, pass it in with your other options.

{ appname: 'whatever' }

plugins

You will need an array of ssb plugins to load, as ssbd has no opinion on plugins; it provides only the ssb-plugins plugin.

const options = {
  ssbd: {
    plugins: [require('ssb-db'), require('ssb-master')]
  }
}
const sbot = ssbd(options)

user plugins

See https://github.com/ssbc/ssb-plugins#load-user-configured-plugins for documentation on installing user supplied ssb plugins.

ssbd loads user plugins before the plugins array. ssb-plugins rejects plugins it has already loaded, therefore user plugins override your application's default plugins.

user config

The ssb application data directory mentioned above may optionally have a json config file (no file extension) with ssb and ssbd config. This config overrides your application's ssb config, as well as the default config set by ssb-config. Because the user must be in control.

example

const ssbd = require('ssbd')
const plugins = require('@metacentre/shipyard-ssb')

const sbot = ssbd({ appname: 'ssb-test', ssbd: { plugins } })

console.log(sbot.address())

cli

To interact with your ssb daemon from the command line, use ssb-server. For debugging, when starting the server, set DEBUG=ssbd to log to console.

acknowledgments

ssbd is inspired by ssb-server

see also

license

MIT