Backupping Workflows

[taner]

Hi Admin Team,

Hope you are fine!
I have a question regarding backupping my FFAStrans workflows.
Is it sufficient to copy the JSON-files within /processors/db/configs/worfklows ?
Would be handy for a automated backup routine.
Or do I have to use the export dialogue within the gui?
Regarding exporting workflows: most of my 80 workflows have specific farming settings and when i export all workflows at once I'm asked for every workflow whether I want to keep the farming settings or not.
A general export setting where one can include / exclude farming settings for all workflows or "let me decide for each workflow" would be nice.
But to be honest thats actually a feature request of the category: powdered sugar on the cherry on the cream cake.

Best
Taner

Edit: I'm constantly changing workflows, adding new ones, deleting old ones. So I have to backup frequently

[emcodem]

Ay Taner,

you could consider using git and just exclude the hosts because these constantly change their files, writing heartbeat date into the jsons. This provides a nice changelog and of course pairs best with Agents, e.g. you can tell them to capture the current state, the agent writes a nice summary into the changelog (commit message) and later you can ask questions about the history.
Other than that, for pure backup purposes and workflows only, i'd recommend to take db/configs/workflows folder, user_variables.json, ffastrans.json, hosts_groups.json and probably even the archive. If you do periodic backup, you could consider just using the latest one i posted here:viewtopic.php?f=5&t=1197&p=9789#p9789, it takes only the stuff needed to get it back up working again and omits all historical information which takes most of the space.

[taner]

Great, thanks !