So we moved our plug-ins, gizmos scripts etc to a central server. We did this by setting our NUKE_PATH with an environment.plist in 

~.MacOSX/environment.plist

That file looks like this, for instance:

While this has been working great for the workstations, when I tried to use rush I got errors about missing plugins and gizmos and the render fails. The render machines are set up the same as the workstations with the same environment.plist. In fact nuke wouldn't recognize the plug-ins if I launched nuke from the terminal i.e. 

So something isn't right. I also noticed that I got the same errors when I tried to ssh into a workstations and run a render. On the nuke list it was suggested I try setting a .bash_profile instead of the .plist method. While this worked for the terminal (and presumably ssh though I forgot to try it) it still doesn't work for rush, and if I want to also be able to launch nuke by double clicking the icon (which I do) it would mean keeping both .bash_profile AND environment.plist files. This seems wrong to me.

Could this be something about users? i.e. rush running as something other than the current user? Can I just put either the .plist or the bash file in a place that makes it appear for ALL users? Do I need to put some kind of "export NUKE_PATH..." in my rush nuke submit scripts?

Anyway, so I'm asking here. How do Mac facilities keep a central install of all their 3rd party tools and init.py etc for both workstations and renderfarms?