Agreed nice and easy for the semi-permanent stuff. Working well at office and approachable for a non techie artist as well.
> On Apr 25, 2017, at 00:49, Diogo Girondi <diogogiro...@gmail.com> wrote: > > If you're not into bash and stuff, the easiest and less tecnical way to set > permanent environment variables on MacOS is by using the EnvPane. > > https://diaryproducts.net/EnvPane <https://diaryproducts.net/EnvPane> > > Cheers, > Diogo > > _____________________________ > From: Howard Jones <how...@axis-vfx.com <mailto:how...@axis-vfx.com>> > Sent: Tuesday, April 25, 2017 04:35 > Subject: Re: [Nuke-users] Re: env on Mac, nuke > To: Nuke user discussion <nuke-users@support.thefoundry.co.uk > <mailto:nuke-users@support.thefoundry.co.uk>> > > > Do the same without the project approach to a central shared location. Set > nuke_path to that. Set /etc/bashrc for all users on a machine and launch from > a shell. > > Howard > > On 25 Apr 2017, at 1:52 am, Gary Jaeger <g...@corestudio.com > <mailto:g...@corestudio.com>> 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 <michaeld...@gmail.com > <mailto:michaeld...@gmail.com>> 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 <g...@corestudio.com > <mailto:g...@corestudio.com>> 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-environment-variable-in-mac-os-x-launchd-plist/ > > <http://www.dowdandassociates.com/blog/content/howto-set-an-environment-variable-in-mac-os-x-launchd-plist/> > > > Gary Jaeger / 650.728.7957 <> direct / 415.518.1419 <> mobile > http://corestudio.com <http://corestudio.com/> > On Apr 24, 2017, at 3:58 PM, Gary Jaeger <g...@corestudio.com > <mailto:g...@corestudio.com>> 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 <> direct / 415.518.1419 <> mobile > http://corestudio.com <http://corestudio.com/> > > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk > <mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ > <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> > > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk > <mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ > <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > <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 (direct) • 650.728.7060 (main) > http://corestudio.com <http://corestudio.com/> > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk > <mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ > <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> > > > A X I S V F X > The Bottle Yard Studios > Whitchurch Lane > Bristol BS14 0BH > > axis-vfx.com <http://axis-vfx.com/> > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
