Save Flows after push to Digital Ocean App

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
cloud, documentation

Research direction

No file, test, or documentation entry point is named. Start by reviewing the sample Node.js application's deployment documentation and how its DigitalOcean App service is configured, then verify how Node-RED flow data is handled across a service restart. Done means a newcomer can follow a documented setup or example that preserves flows.

Written by the indexing model from the issue text.

Description

I can get NodeRed to run and even build flows that work and deploy them. but once I restart the service all my work is done. It says to load it with a -v setting but I cannot find anywhere to add this setting. Can someone provide better documentation or examples of how you set it up to keep your flows after building. For the record I spent hours building some flows and lost every bit of it. LOL

Dominant language
JavaScript
Stars
84
Forks
531
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from digitalocean/sample-nodejs

All issues in digitalocean/sample-nodejs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.