GUI for the recently added FileBot-Node API
Posted: 11 Jul 2019, 00:30
Background Scenario:
I'm currently running filebot 4.8.5 and filebot-node 0.2.8.5 natively on a headless ubuntu server.
I get my media from multiple sources and hence it gets downloaded to different folders.
i have set up predefined task using the new api that was introduced with filebot-node 0.2.8.3. However as i have multiple tasks that i have set up, i find it hard to recall what task id is associated with what action. I therefore end up remotely logging i to the server to run filebot individually on the folders.
i was wondering if the following could be implemented in filebot-node.
1. a descriptor for the task " rename Movies in folder XXX or rename Music is folder YYY" - this should be user editable
2. a button "Execute Preset Task" in the filebot-node gui which when pressed will give you a drop down menu to pick a task using the descriptor set above or task id if no descriptor is available.
i understand that this maybe a niche request, but i think this will help all those who are running a headless server.
Thank you
I'm currently running filebot 4.8.5 and filebot-node 0.2.8.5 natively on a headless ubuntu server.
I get my media from multiple sources and hence it gets downloaded to different folders.
i have set up predefined task using the new api that was introduced with filebot-node 0.2.8.3. However as i have multiple tasks that i have set up, i find it hard to recall what task id is associated with what action. I therefore end up remotely logging i to the server to run filebot individually on the folders.
i was wondering if the following could be implemented in filebot-node.
1. a descriptor for the task " rename Movies in folder XXX or rename Music is folder YYY" - this should be user editable
2. a button "Execute Preset Task" in the filebot-node gui which when pressed will give you a drop down menu to pick a task using the descriptor set above or task id if no descriptor is available.
i understand that this maybe a niche request, but i think this will help all those who are running a headless server.
Thank you