Skip to content

Latest commit

 

History

8 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Enabling version control for Node RED flows.json in the VanPi

This is a small wrapper that should allow you to introduce version control via Git to the VanPi Node RED development workflow.

The approach taken here is loosely based on this tutorial.

Requirements

  • Docker
  • A MacOS or Linux machine (for the bash scripts provided, which can otherwise easily be rewritten for Windows)

Getting started

  1. Clone this repository on your local machine within a directory of your choice
  2. From the folder in which you cloned the repo, run:
    ~$ ./create-node-red-docker.sh
    ~$ ./start-node-red-docker.sh
  1. Create your own fork of the VAN_PI repository, which is where you will develop custom features and keep in sync with the original project
  2. Open Node RED at http://127.0.0.1:1880/ and start a new project by clicking on "Clone Repository"
  3. Provide your username and email address and click "Next"
  4. Copy-paste the SSH address of your cloned VAN_PI repository into "Git Repository URL"
  5. Click on "Add an ssh key" and copy the obtained public key into your GitHub SSH keys
  6. You might need to refresh Node RED in your browser and start adding the repository again, following the steps above, after closing the SSH window
  7. Click on "Clone project" and wait (this might take a few minutes)
  8. You will get a "Project package file not found" error. Click on "Setup project files"
  9. Next to Files, click "edit" and point Package and Flow to /VanPi-OS/package.json and /VanPi-OS/flows.json
  10. Click "Save"

You should now be able to develop in Node RED and push / pull changes to your forked Git repository. I suggest watching this video for a demonstration of how the development workflow looks like.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages