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

@insectos/node-red-cloudflare-ddns

v0.4.0

Published

A DDNS client for Cloudflare with optional distributed operation

Downloads

13

Readme

@insectos/node-red-cloudflare-ddns

Cloudflare does not offer a DDNS client on the free plan. This node closes the gap.

Node that checks the public IP address of the current NodeRED instance using ipify. When the IP address doesn't match the cached value, calls the Cloudflare API to correct the value. The cached value is retrived from context on startup. Works with Cloudflare cached ip addressen too.

Preparation

You need to login to your Cloudflare account and perform the following steps:

  • Find your ZoneeID. We only need the ZoneID here.
  • Create a Cloudflare API Token. Limit it to your Zone. It needs DNS edit permisssions
  • Create an A record (AAAA not yet) for your DDNS site. Add a comment tha begins with [DDNS] (Case sensitive)

Usage on a single node

Add the Node to a page, use a button or a timer to trigger it.

Use a Catch node to see what errors are thrown from the DDNS node that aren't already being caught and handled.

Input

Anything: input values are ignored, used only to trigger the lookup

Output

msg.payload <json>

{
  "ip": ["123.123.123.123", ...],
  "updated": false /* Not updated since the last run */
}

Usage in the hub-spoke mode

In the Hub-spoke model the Cloudflare credentials are only maintained by the hub. This is kind of a service provider scenario. We use it on distributed farms where we can't control the access to hardware and don't want to distribute cloudflare credentials.

See the examples for a configuration

Spoke

  • Configure the hub URL including a path
  • Configure the token to identify the spoke
  • Use a button or timer to trigger it
  • Use a http request node to talk to the hub

Hub

  • Configure the list of spokes and their tokens
  • use a http in and a http response to handle spoke submissions

Libraries used

  • Mocha, Chai, Sinon for testing
  • No Runtime dependencies beyond NodeRED

Change log

v0.3.0

  • moved host & tokens to editable list

v0.1.0

  • moved nodes to Cloudflare category
  • Introduced hub & spoke nodes for central operations
  • pass through msg object to be a good Redicen (NodeRED citicen)

v0.0.1

  • Initial creation

Ideas & Feedback

The Spoke component is useful even without Cloudflare and the hub component. Running it will provide you with your public IP address in the payload