Gary, I took this off-list to save everyone from a semi-long email!
Michael On 24 April 2017 at 20:52, Gary Jaeger <[email protected]> wrote: > Interesting, thanks Michael. So you're setting name aliases in > .bash_profile per project? I do think we want a more generalized approach. > What's an example of what you are customizing between projects? > > On Mon, Apr 24, 2017 at 5:36 PM, Michael Garrett <[email protected]> > wrote: > >> The general approach is to define NUKE_PATH for that project, for the >> custom nuke environment (like the .nuke folder but on the network). Then >> you have the custom init.py, menu.py and gizmos etc living there. For >> example, the most basic way of doing it in .bash_profile on OSX: >> export NUKE_PATH="path/to/your/project/pipeline/nuke" >> >> If you want to abstract it a bit more, set an abbreviated name alias for >> the project which you can set up to take you to the working directory and >> also set the NUKE_PATH for that project with all the customisations. That >> way, you can easily switch between projects with a new shell and when you >> launch Nuke you will get the relevant customised version. I've actually >> never tried to get environment.plist working, but it does seem like a pain >> and it's easier to repurpose scripting and variables between OSX and Linux >> (and now Windows 10??) when sticking to using a bash terminal. >> >> On 24 April 2017 at 19:26, Gary Jaeger <[email protected]> wrote: >> >>> OK, answered my own question. Looks like creating an environment.plist >>> in ~/Library/LaunchAgents/ does the trick. >>> >>> now another. do you all create an init.py and menu.py on each >>> workstation? I tried creating a simlink to files on a central server, which >>> seems to work, but not sure if there are downsides to that approach? Trying >>> to keep the admin to a minimum. >>> >>> Thanks >>> >>> http://www.dowdandassociates.com/blog/content/howto-set-an-e >>> nvironment-variable-in-mac-os-x-launchd-plist/ >>> >>> >>> *Gary Jaeger */ 650.728.7957 <(650)%20728-7957> direct / 415.518.1419 >>> <(415)%20518-1419> mobile >>> http://corestudio.com >>> >>> On Apr 24, 2017, at 3:58 PM, Gary Jaeger <[email protected]> wrote: >>> >>> Where is the current place to set env variables on the mac? Googling >>> gives me various answers, none of which I can really get to work. The >>> latest (and what the foundry docs say) seems to be launchd.conf, but for >>> instance if I put >>> >>> setenv NUKE_PATH /Volumes/tools/nuke10_5 >>> setenv OFX_PLUGIN_PATH /Volumes/tools/nuke10_5/OFX >>> >>> they don't seem to get picked up >>> >>> also, what’s the difference between ‘setenv’ and ‘export’ ? >>> >>> thanks >>> >>> *Gary Jaeger */ 650.728.7957 <(650)%20728-7957> direct / 415.518.1419 >>> <(415)%20518-1419> mobile >>> http://corestudio.com >>> >>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> >> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> > > > > -- > Gary Jaeger // Core Studio > 249 Princeton Avenue > Half Moon Bay, CA 94019 > 650.728.7957 <(650)%20728-7957> (direct) • 650.728.7060 <(650)%20728-7060> > (main) > http://corestudio.com > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
