You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Preload/Restore Chatflows, Agents and Tools from github/zip
Linking Flowise to a DB is very useful indeed. Yet, when setting up new or reconstituting an environment from scratch for development or to simply use as a sandbox, it would be useful if all flows and tools could be loaded from an alternative source.
In addition to postgres, when making changes to flows/tools, we usually save each revision to github (to mantain feature parity with our release cycle).
Sometimes we want to keep alternative instances of flowise for a multitude of reasons. Being able to reconstitute a fully functioning 'standalone' flowise instance is extremely useful (when we're developing on the move, etc).
It would be a nice feature if we can rebuild said instance from either a zip file or even from a github repo. Maybe with a convention folder structure, eg:
Preload/Restore Chatflows, Agents and Tools from github/zip
Linking Flowise to a DB is very useful indeed. Yet, when setting up new or reconstituting an environment from scratch for development or to simply use as a sandbox, it would be useful if all flows and tools could be loaded from an alternative source.
In addition to postgres, when making changes to flows/tools, we usually save each revision to github (to mantain feature parity with our release cycle).
Sometimes we want to keep alternative instances of flowise for a multitude of reasons. Being able to reconstitute a fully functioning 'standalone' flowise instance is extremely useful (when we're developing on the move, etc).
It would be a nice feature if we can rebuild said instance from either a zip file or even from a github repo. Maybe with a convention folder structure, eg:
The text was updated successfully, but these errors were encountered: