Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplified Flow Synchronization #1054

Closed
nichols89ben opened this issue Aug 11, 2024 · 7 comments
Closed

Simplified Flow Synchronization #1054

nichols89ben opened this issue Aug 11, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@nichols89ben
Copy link

Hello!

I’m looking for a more efficient way to share identical flows across multiple servers. I currently manage one master flow that meets all my needs. Previously, I would make an edit, then copy and replace the entire FlowsJSONDB in each of the other DB2 files, restart the servers, and everything would update seamlessly.

However, with the recent update to the SQL DB, I now have to manually paste the flow into each DB. While I’m aware of the “export to clipboard” and “paste from JSON” features for new flows, using them seems to change the flow ID and disrupts the linkage of some “go to” flows.

It would be incredibly helpful to have an “update flow from JSON” feature or the ability to edit the JSON flow directly within the UI, similar to how plugins can be edited.

Thank you!

@nichols89ben nichols89ben closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
@HaveAGitGat HaveAGitGat reopened this Aug 14, 2024
@HaveAGitGat
Copy link
Owner

This is still planned 👍

@HaveAGitGat HaveAGitGat added the enhancement New feature or request label Aug 14, 2024
@nichols89ben
Copy link
Author

This is still planned 👍

Cool, I knew you had a lot going on with the switch so I thought it could wait.

@HaveAGitGat
Copy link
Owner

In 2.24.04 when you export a flow it will export the _id so when you import several flows that depend on each other it should work fine. Is this ok?

@nichols89ben
Copy link
Author

In 2.24.04 when you export a flow it will export the _id so when you import several flows that depend on each other it should work fine. Is this ok?

Yes, that should work fine. I liked the ability to drop and replace the flows via the files, then start the container, keeping the libraries with the assigned flow intact. This method still makes it easy, just need to delete the old flow first and then reassign it in the library. Will changing the flow in the library, like designating a new flow, trigger a requeue? I also noticed that some of the flow plugins Migz posted earlier are now incompatible with the new version 🥴

@HaveAGitGat
Copy link
Owner

No changing a flow does not requeue files, that needs to be done manually. Which Migz plugin are you having trouble with? There haven't been any changes to the community ones in a few months.

@nichols89ben
Copy link
Author

No changing a flow does not requeue files, that needs to be done manually. Which Migz plugin are you having trouble with? There haven't been any changes to the community ones in a few months.

He posted them as Experimental flows in Discord awhile ago and I grabbed them. Actually the only one I use that has an error is the Check Stream one. It was a very handy way to filter all A/V/Sub streams. Lmk if you know of something I can adjust to get it going or what I could use instead. I haven't gone through updated community flows in a minute.

Experimental Flows.zip

@HaveAGitGat
Copy link
Owner

Sorry for the delay but if you're still having trouble could you post the files not in a zip at https://github.com/HaveAGitGat/Tdarr_Plugins thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants