Enable / Disable persistent file nodes & context in my FlowForge platform projects

[Steve-Mcl]

Epic

212

Description

As a: Owner / Admin

I want to: Enable / Disable file nodes in my FlowForge platform

So that:

• Some projects have persistent context
• Some projects have persistent file storage
• Some projects have both
• Some projects have none

As discussed here: https://github.com/flowforge/flowforge/pull/1465#discussion_r1053212248

Current situation:

File storage can be enabled/disabled globally for a FlowForge Instance by adding/removing the fileStore block in the flowforge.yml If enabled then disabling the core file nodes will enable the FlowForge File Nodes There is currently no way to have projects with a mix of some with node file nodes at all and some with the FlowForge Nodes.

Which customers would this be availble to

None

Acceptance Criteria

• [ ] Include Tests
• [ ] Update documentation
  • [ ] readme docs
  • [ ] cloud docs
  • [ ] flowforge docs

[knolleary]

Focussing on the file nodes:

1. You get the Core file nodes by default (ie, nothing adding to the Project Template)
2. You get the FF File nodes if:
   • fileStore configured in yml
   • 10-file.js added to the 'Exclude nodes by filename' in Project Template

If an Admin wanted to disable the File nodes entirely - both core and our custom ones - but still have fileStore configured for Persistent Context, then I believe they should be able to:

1. Add 10-file.js to 'Exclude nodes by filename' in Project Template
2. Add @flowforge/nr-file-nodes to the 'Prevent Install of External nodes' section of the Project Template

That should be sufficient but needs to be verified.