I decided to record a series of interviews dedicated to people living and working abroad in California. This interview is with my good friend, artist and developer Sergii Dumyk. I met him under unexpected circumstances and since then follow his unusual way of exploring San Francisco.
By using standard command line Shotgun (SG) activation SG create project config that attached to the main “studio” configuration thus it’s not localized and not portable.
Command line based activation
By using “localize” Tank command config can be imported into single self contain folder that can be copied anywhere.
But copy of this config have no use until it hooked up with SG project. What if we want to hooked it up with the project that already has a internal studio config. In this example I brought a copy of my config home.
You will get permission denied error if you create “sg” object by authenticating “humanUser”. Shotgun object has to be constructed from API script.
Since the path where I want to store my project at home doesnt necessary match my studio setup we want to tell Shotgun where to look bu configure Local File Storage in SH Website Preferences.
There are couple files that need to be corrected in you duplicated config folder that it corresponds with the new Pipeline Configuration on SG website.
config/core/pipeline_configuration.yml should look something like that
I mounted “Z:” network drive to make it consistent among all external artist.