Env variable for module loading?

[jeffd]

At our studio we like to keep all of our scripts and plug-ins on the network in source control, so as new versions are released it is very easy to update them and keep everyone on the same page.

I am trying to devise a plan to get Bonus Game Tools for 5.0 in this setup. The catch for me is that the 5.0 version of these tools uses the new module setup for installing. The catch for me is that I really would like to centralize the user/modules directory so I can have just one place where everyone goes to get these files instead of having to support it across everyones local user directories. Thoughts?

--JeffD

[warpcat]

We use Alienbrain for source controll here. Basically, everyone maps their Z: drive to the AB server. In AB, we have a z:toolsartToolsscripts & plugins dir, where any project related scripts go. Maya's sript path is set up to source these dirs. Then, it's really easy for someone to do a get in AB on tools, and instantly all their scripts are updated to current. Even if you don't use AB, you can still have them map a network drive (with a consistant letter) to your server where your scripts live. Of course, everyone would need to have their Maya.env or their Windows prefs updated with the new paths, but it should work.

[jeffd]

We also use AB and centralized tools in almost the exact same way you describe. We currently use system environment variables on each users machine for MAYA_SCRIPT_PATH and MAYA_PLUG_IN_PATH. I really am hoping to find a way to have maya load either the modules file or maya.env from a centralized location as well. It would be the same for everyone and that way I could change it as needed.

The problem is that the only way I see to do it is to use MAYA_APP_DIR. The problem with this is that this then forces all users prefs to this location. Granted those would all be local files to the user, but I would prefer to not mix local files with the source control stuff.

--JeffD

[joojaa]

Doesent maya have a switch for wich env file to read on startup! In the command line that is. You could then proceed updating all links to point to 1 spesific env file...

[jeffd]

Actually, I just stumbled across MAYA_MODULE_PATH which does pretty much what I need.

I am going with a setup in which we define the following environment variables on each user's machine...

MAYA_MODULE_PATH = source controlled directory
MAYA_SCRIPT_PATH = source controlled directory

The module path allows me to add plugs, scripts, icons, etc in a very organized way and do selective loading should I so choose without having to modify each users env vars.
I had to use the script path because we have a a couple scripts with the same name as out-of-the-box scripts which add to the base functionality of standard UIs. Since module script paths have a lower search priority than default script paths, I have to use this env var to be able to override the out-of-the-box scripts.

Thanks for the input everyone. If you aren't familiar with module setup, you should realy look into it. It seems to be a great way to organize a directory of scripts and tools without the need to constant maintain paths in env vars.

--JeffD