local projects export / import

[forresto]

From the design side, we should be clearer that local projects are tied to a particular browser.

We should also make tools for exporting JSON of all / selected projects, and importing. This would be useful for backup, moving to a different browser, and migrating to https://app.flowhub.io/ from http.

Maybe don't need the whole journal, unless that's easy?

[bergie]

@forresto I think GitHub should be enough for this purpose

[forresto]

Local stuff should have this offline option.

[jonnor]

I think we should allow import of a graph, to be symmetrical to export. Whole-project syncronization I think is fine to have only through github.

[bergie]

@jonnor one option would be to accept dragged files (JSON or FBP becomes a new graph, others become components)

[ryedin]

@bergie github is not necessarily the end-all here. For private projects it would be much nicer to point to a local git repo. While the generic essence of that is actually just 'save to disk' (and is thus already supported by manually exporting each graph and component one at a time), an automated hook into the journal editing pipeline that allows us to save to and load from wherever we want is what is truly needed.

I'm not sure if the onus is on the ui, the runtime, or both for something like that but the ability to sync to disk, or CouchDB (for example) in an automated way would be spectacular. Maybe the hooks are all already there? This is an area I plan to look into.

[ijsf]

Would be very useful for those hosting their own (internal) noflo deployment.

[chadrik]

I think it would be good to have a pluggable GraphStore type. When you build noflo-ui you can choose which stores you want to include, and add your own. Currently we have "browser" and "github", but I could also see using mongo or another db, a simple folder of .fbp files, or a git repo like @ryedin mentions.