![]() In the out-of-the-box setup, files are published in place, which avoids the need to define templates or filesystem schema. The Publisher is designed to ease the transition between the out-of-the-box workflow and the full pipeline configuration. Just choose ‘Legacy Default’ when prompted to select a configuration in the Desktop Set Up Project Wizard. : Looking for the old config structure? With the v1.1 release of Integrations, we reorganized the structure of the Default Config to help maximize efficiency and readability, and to make it match the Basic Config’s structure more closely You can still base projects on the legacy Default Config. For a detailed description of the Default Config’s structure, see the config/env/README.md file in your Pipeline Configuration, or view it here in Github. You can see the Default Config in Github here. It includes filesystem location support and a wider array of Toolkit apps and engines. This is the default starting point for our Advanced project setup. You can subscribe to release notes here, and see the Basic Config in Github here. When you use out-of-the-box integrations on a project, your copy of the Basic Config is auto-updated whenever you launch Desktop, so you’ll always have the latest version of our integrations. The Basic Config does not include filesystem location support. The Basic Config makes three Toolkit apps – The Panel, Publisher, and Loader – available in all supported software packages, and looks to your Software Entities in ShotGrid to determine which software packages to display in ShotGrid Desktop. When you use our out-of-the-box integrations, there’s nothing to administer, but Toolkit uses an implied Pipeline Configuration under the hood, and we call this Pipeline Configuration the Basic Config. Our out-of-the-box integrations are designed to run without the need to set up or modify any configuration files. The Pipeline Configuration is highly customizable, but we offer two starting points. Standard Pipeline ConfigurationsĪt the heart of any Toolkit setup is the Pipeline Configuration, a set of YAML files that manage everything from installed apps to software versions, and in some cases, even hold the templates for setting up your production directory structure and file names. This document falls between those two: it’s intended for those who are implementing ShotGrid integrations for a studio, managing software versions, and making storage decisions for published files. Our User Guide is intended for artists who will be the end users of ShotGrid integrations in their daily workflow, and our Developer Guide is technical documentation for those writing Python code to extend the functionality. It’s one of three: user, admin, and developer. This document serves as a guide for administrators of ShotGrid integrations. ShotGrid Integrations Admin Guide Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |