AWS Thinkbox Discussion Forums

"custom" directory - organisation vs. chaos

Deprecated Deadline 6 Beta Discussion
#1

Hi,
I thought I had requested this ages ago but maybe not? I have lots of custom “general” scripts which using the new flat py file folder layout structure is going to be a headache.
I’m ok with script visible name, icon path and permissions…it’s because some of my general scripts have 1 or more accompanying exe’s / py modules (which are not named the same as the py file as they are 3rd party), which get executed as part of a particular general script. When you scale up the number of general scripts (>30), then your “custom” > “scripts” > “general” directory soon becomes a complete mess!

Can all the “custom” directories be recursively scanned for py script files, instead of the root directory? Any additional py files it picks up which may be for referenced in modules or such like, can still be picked up in this ‘scan’, but can be safely ignored by making them NOT visible via the Deadline Scripts Menu UI enable/disable functionality.

Then, I can create sub-folders in any of the custom directories and it’s not a mess. Doesn’t affect Thinkbox as this directory structure isn’t updated? Extend this concept to all the custom directories?

Thanks,
Mike

#2

That seems a bit hackish, especially if other .py scripts in subfolders end up showing up in the Scripts configuration window. Also, it would definitely be a performance hit if the repository is remote (that was the main reason we switched to having all the scripts in one folder).

Could you not just create a subfolder in the same folder as the scripts, give it the name that matches the script it’s for, and then store your extra .exes and .py files in there? That should still keep things pretty clean I imagine…

#3

Ok. Good call. Performance is king.

#4

Which brings me to another old point. The Foundry compile py to pyc on first execution. Is there a performance win to be had if Deadline did the same thing?

#5

Compiling isn’t really the issue. It’s performing the directory scans on a remote server that can be slow.

Privacy | Site terms | Cookie preferences