With ftrack, you can track asset files on a digital asset management system or storage system. ftrack achieves this via a concept known as “storage locations”. Registering an asset file in ftrack is called Publishing and results in a new asset version.
You can have one or several storage locations representing different types of storage across multiple sites if necessary.
Configure a storage scenario
By default, assets are published to the "ftrack.unmanaged" location which means that files are not touched and paths are just recorded at components as they are. By setting up a storage scenario, or registering a managed location in general, publishing via API, Connect and DCC app integrations will cause files to be moved based on the registered Structure (default: ftrack_api.structure.standard) and Accessor (default: ftrack_api.accessor.disk) to its correct location upon publish.
ftrack comes with support for disk-based storage location or Perforce by default.
If you have traditional disk-based storage – for example, a network mounted NAS – it is possible to configure that using the centralised storage scenario.
Another default scenario is the perforce storage scenario, which you can also configure to your needs.
Building your own custom location plugins
If you want more control over how file paths are generated (Structure API plugin) or wish to use custom storage like Amazon S3, Dropbox or FTP, etc. (Accessor API plugin), it is possible to develop a location plugin to the Python API.
- Configuring file storage
- Publish local files as versions
- Perforce version control