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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gregoriusrippenstein/node-red-contrib-flowhub-server

v1.1.0

Published

FlowHub.org: flow management with local Git

Readme

Local Git Store for Node-RED

Local Git storage for Node-RED flows

This package defines the flows that are required to install and run a local Git store for the usage with the FlowHub.org node package.

The aim is to enable local git usage for maintaining visual flow code using a visual version control approach based on Git.

This installs no nodes nor plugins, the package only provides example flows that, when installed, provide the backend for the FlowHub.org nodes. This package is slightly larger (ca. 20MB) but that's because it contains third-party JS code for the Webiliser frontend.

That allows this to be executed completely offline, including the Webiliser frontend.

Introduction

FlowHub.org provides visual change management (aka version control) on top of GitHub. FlowHub Local (aka FlowHubⓁ) is a local-first server for the FlowHub.org nodes, replacing the GitHub requirement.

FlowHubⓁ provides a local gitstore for managing change made to flows, locally, no internet connection is required. FlowHubⓁ is used in conjunction with the FlowHub.org nodes but provides a local gitstore, replacing GitHub.

FlowHubⓁ has a client-server architecture with both client and server being installed in Node-RED instances. The client and server are both Node-RED node packages that can be installed into any Node-RED instance.

FlowHubⓁ is designed to be installed on a central instance of Node-RED and multiple clients connect and communicate with that installation of FlowHubⓁ.

This solution was inspired by the Local First Conf initiative.

Installation

Installation is described in the installation guide.

FlowHub.org Token definition

To use this backend server, the FlowHub.org nodes need a token that points to this server. This requires that the hostname of the server needs to be added to the token.

Tokens for local servers always begin with local:// followed by the hostname of Node-RED hosting the backend examples/flowhub-local-server.json flow.

For example, a valid local token would be:

local://https://gitstore:1880/store/gerrit/screencast1/main

Explanation:

  • local:// is the token prefix for a local token, c.f., a FlowHub.org remote token is prefixed with fhb_.
  • the Node-RED host is reached via https://gitstore:1880. HTTPS isn't required but is recommended.
  • /store/ is the path specified needs to be included
  • gerrit/screencast1/main is the username to commit changes with, screencast1 is the repository name which corresponds to the directory name in the repos directory. main is the branch and should be used by default.

Changes to settings.js

Some changes need to be made to the settings.js file to support the larger flow size.

    /** The maximum size of HTTP request that will be accepted by the runtime api.
     * Default: 5mb
     */
    //apiMaxLength: '5mb',

because of the size of the CDN flow, this needs to be changed to at least 25mb

    /** The maximum size of HTTP request that will be accepted by the runtime api.
     * Default: 5mb
     */
    apiMaxLength: '25mb',

Using SSL Certificates

There is a post describing how to do that for Node-RED.