With local file linking, you have the option of pointing to a local networked file system rather than uploading files to Shotgun. You can even configure multiple mounted volumes, and specify different file mounting prefixes for Mac, Windows, and Linux users.
Local file linking requires the Shotgun Desktop app. You can download the app from the Apps menu of your Shotgun site.
Admins can go to the Admin > Preferences page, then click to expand the File Management section. Make sure you check the preference, 'Enable linking to local files'. Once this is done, click 'Save Changes'.
Next, click the 'Add Local File Storage' link to create a new mount point. You’ll see that this brings up a widget where you’ll enter some information.
Note: You can use relative paths. For Windows, you will need to use
//machine-nameas the prefix to
/proyects/shotgun. Additionally, machine-name should be a machine or server that everyone on your network can access.
Create multiple mount points
You can create multiple mount points by clicking the [+] Add Local File Storage link once for each additional mount point. We recommend not getting too specific here. If you access most of your files from a project directory, such as "C:\projects", we recommend pointing to that directory instead of something like "C:\projects\this_one_project\files". This will make maintaining your local file storage easier as you add more projects.
Name the mount point
Give the mount point a human-readable name (e.g., Element Library), and then fill out different path prefixes for each operating system that has the networked resource mounted to it.
Note: You don’t have to fill out every operating system file path prefix. So, if you’re a Windows only studio, just fill out Windows.
Save your changes
Click 'Save Changes' to save the newly created mount point. As soon as you do this, people can start creating files in Shotgun that just point to files inside of the networked Element library.
Once you have a mount point set up, clicking to open files in Shotgun is super fast. With local file links, you’re not actually uploading anything. Instead, Shotgun stores the paths to the files so that the applet will know how to find them on your computer. By doing this, you can keep huge files on your network volumes, but still have access to them within Shotgun.
Example: Create three reference art files with local file links
Bring up a new file entity creation form, click the 'Link to Local' tab, then 'Browse'. Once you get to your networked volume—/Volumes/Elements/—attach three files. Click 'Choose', and then enter a description of 'Reference'. Then click 'Create File'.
Go to a files page to look at the three files you just created with local file links.
Note on auto-generated file attributes
Locally linked files will never result in auto-generated thumbnails, as would normally be the case if you uploaded an image file. Thumbnail images will have to be uploaded to the server. Also, the File Name, File Type, and File Size fields will never be auto-generated. You can use the API to automate this process. Read more about working with files and the API in the "Working With Local File Types" section of our API documentation.
When you view a local file link in Shotgun, it appears just like a normal link. Clicking a local file link from within Shotgun is exactly the same as double-clicking a file on your desktop. So, if you’ve got Photoshop installed on your computer, and that’s the application that is registered to open files of type .psd, you’re one click away from opening local file links to .psd files in the native application.
If you’re attempting to click on or view local file links from outside of the network, the links will appear as links, but clicking on them will result in a dialog like the one shown below.
Definitely. In the File Management section of your preferences page, you can click the 'Add Local File Storage' link multiple times to create several mount points.
Yes! The Python API now supports local files as of v3.0.3. You can both read and modify local file links using the API now.