In my older nuke init.py I have some code that looks like this:
def run():
plat = FIE.Platform.GetCurrentPlatform()
fieloc = FIE.Platform.GetFIELocation()
verstring = nuke.NUKE_VERSION_STRING
nukeplugpath = os.path.join(fieloc, "NukePlugs")
nukeplugpath = os.path.join(nukeplugpath, plat)
nukeplugpath = os.path.join(nukeplugpath, verstring)
nuke.pluginAddPath(nukeplugpath)
nukeplugpath = os.path.join(fieloc, "NukePlugs")
nukeplugpath = os.path.join(nukeplugpath, "All")
nuke.pluginAddPath(nukeplugpath)
where: fieloc is a rootpath for my tools. As you can see, I have it
dynamically adding nuke plug in paths based on what version and platform is
running, as well as a common "all" plug ins directory.
In my setup, the tools are checked out to each workstation via subverison. but
in other facilities i've worked at, similar things have been done with nfs
network shares without issue.
Also, I have seen nuke itself run from a network install location without issue
quite successfully.
On Feb 25, 2011, at 7:26 PM, Gary Jaeger wrote:
> What's the best way to keep nuke installs consistent between workstations?
>
> We're a small shop and we've always done it seat of the pants (which is
> manageable given our size) but I have a feeling there is A Better Way.
>
> . . . . . . . . . . . .
> Gary Jaeger // Core Studio
> 86 Graham Street, Suite 120
> San Francisco, CA 94129
> 415 543 8140
> http://corestudio.com
>
> _______________________________________________
> Nuke-users mailing list
> [email protected]
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
Bradley Friedman
VFX and Animation
Consulting and Technology
http://www.fie.us/
[email protected]
_______________________________________________
Nuke-users mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
