Skip to content
This repository was archived by the owner on Jul 16, 2024. It is now read-only.

Documentation

manneohrstrom edited this page Oct 29, 2012 · 6 revisions

Welcome to the Tank Default Config. This config is for demo purposes and is a good way to get an overview of what apps are available with Tank and how Tank can integrate with an existing pipeline.

The configuration contains a number of different pieces:

  • A file system setup
  • A set of templates to identify key locations on disk
  • A set of preconfigured engines and apps which are chained together into a workflow.

The file system setup is minimal, focused on providing a demo and overview of Tank rather than being a fully featured file system. We strongly suggest that you get in touch with the Tank team if you need assistance when setting up file and folder structures with Tank.

File System Overview

The standard config handles Assets and Shots in Shotgun. It breaks things down per Pipeline Step. A pipeline step is similar to a department. Each pipeline step contains work and publish areas for the various supported applications. The Shot structure looks like this:

![Folders](images/folder_structure.png)

Applications and workflows

The config contains the following components:

  • Maya, Nuke and Motionbuilder support
  • Shotgun Application Launchers
  • Publishing, Snapshotting and Version Control
  • A Nuke custom Write Node
  • Shotgun integration
  • A number of minor tools and utilities

In addition to the apps above, you can easily install additional apps and engines once the config has been installed.

Clone this wiki locally