luangarcia / nodered-heroku

Just aNO(t)DEr nodered for heroku

nodered-heroku

A wrapper for deploying Node-RED into the Heroku.

• DEMO: Flow Editor - https://nodered-heroku.herokuapp.com/editor
• DEMO: Dashboard UI - https://nodered-heroku.herokuapp.com

Warning: You will lost all saved flows every time heroku restart!

• SOLUTION: To overcome this, on Editor, after finish with your design and deployed, you need to Export 'all flows' as "flows.json" file, and push your "flows.json" to your github, linked to your heroku. Detail on step 4 and 5.

1. Deploying Node-RED into Heroku

2. Set Username and Password for your Flow Editor

• NODE_RED_a_USERNAME - replace this with Username for Flow Editor
• NODE_RED_b_PASSWORD - replace this with Password for Flow Editor

3. Access your Node-Red

• Flow Editor - change-with-your-heroku-app-name.herokuapp.com/editor
• Dashboard UI - change-with-your-heroku-app-name.herokuapp.com

4. Export all flows as "flows.json" file AFTER you create your flow and deploy it

• In Editor, click hamburger icon (top right), click Export, choose tab "all flows", then Download.

5. Fork this repo, Set your github as deploy source on Heroku setting, and enable Automatic Deployment

• Push downloaded "flows.json" file to your repo on github.
• Every time "flows.json" pushed to your repo, Heroku will rebuild node-red with updated "flows.json".
• So your node-red will always have latest pushed "flows.json" when Heroku dynos restarted.

*Some included nodes

• Dashboard UI - node-red-dashboard
• MQTT - node-red-contrib-aedes
• Blynk Cloud - node-red-contrib-blynk-ws
• Email - node-red-node-email
• Telegram - node-red-contrib-telegrambot