We’ve been giving some more thought to what it would take for us to deploy Deadline as our primary queue manager, and one of the things that came up that has been in the back of my mind since the beta started is the permission requirements for the repository tree.
In short, the idea that the permissions for the entire tree need to be wide open is kind of crazy, especially if you consider mounting the share as a special (effectively unrestricted) user. I understand why the client needs to be able to create files in certain places in the tree during submission, but I feel like there should be a more elegant (or at least more controlled) solution.
Can you provide a better idea of which directories/files need to be writable by regular users for day-to-day use?
This requirement isn’t a strict requirement now that we’ve moved most of the data into the database. We’ll have to make sure we document this in the v6 documentation. Baseically, the folders that need write access for typical users are as follows:
jobs
jobsArchived
reports
That should be it. Note though that if the user does not have write access to the plugins and events folders, they won’t be able to configure the plugins and events from the Monitor. That’s probably fine for you guys though, since I imagine you would only want certain users changing those settings anyways.
Thanks Ryan, that’s good to know. I was going off of what is currently in the Deadline 6 documentation PDF, which mainly suggests opening the perms up completely (though that could just be legacy information copied from Deadline 5).
Yeah, that would have been legacy information. We’ll definitely be focusing more on documentation once 6.0 is mostly feature complete and we’re in “maintenance” mode.