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

ilp-connector-cli

v4.0.2

Published

Simple tools start ILP connectors

Downloads

6

Readme

ilp-connector-cli npm

Utility scripts to configure and start connectors on ILP

Installation

npm install -g ilp-connector-cli

Usage

Configuring

In order to configure a connector, all you have to do is run ilp-connector-config -o connector.list. This will create an environment file called connector.list, which can be used by Docker (see 'Running'). A command-line interface will walk you through the required steps.

First, the CLI will ask for some general options. These options will be assigned to the environment variables specified in ILP-connector's README. You can see and change these settings by reading connector.list after ilp-connnector-config is done.

Next, the CLI will prompt you for the number of plugins your connector will use. Plugin-specific questions will be asked in order to create appropriate configurations for each plugin. Note that if your ids are not unique, then you may overwrite other plugins. You can edit the final output in the CONNECTOR_LEDGERS field of connector.list. It is output in the form of a stringified JSON object.

Running

The environment file output by ilp-connector-config can be used by docker in order to start a connector. Just run:

$ docker run -it --rm --env-file ./connector.list interledgerjs/ilp-connector

Giving access to others

To run a connector which can be connected to from different machines, you will need to forward your ports. You can use localtunnel to temporarily do this without requiring remote hosting or network configuration. Just run:

$ lt --port 4444
your url is: http://senedqjwk.localtunnel.me

If you are configuring a new connector, then enter that URL when it prompts for your public URI. Otherwise, go into your existing environment file and change the line:

CONNECTOR_PUBLIC_URI= #.....

to:

# write the URL that you got from the previous step instead of this URL
CONNECTOR_PUBLIC_URI=http://senedqjwk.localtunnel.me