Skip to main content

Customising a launcher

This example assumes basic knowledge of the Connect application launcher and its configurations.

In this example, we are going illustrate how to reconfigure the application search paths for Nuke Studio, to point to a network drive shared installation.

Setting up Connect​

To provide your own launcher overrides, create a folder were your Connect extensions should live set the FTRACK_CONNECT_EXTENSIONS_PATH to point to it. Here is an example were extensions would live on mounted network share pipeline in Linux:

export FTRACK_CONNECT_EXTENSIONS_PATH=/pipeline/ftrack/extensions/connect

Creating the launcher customisation​

Then create your override, for example redefining were Nuke Studio is installed:

/pipeline/ftrack/extensions/connect/launch/nuke-studio-launch.yaml:


type: launch_config
name: nuke-studio
search_path:
  linux:
    prefix:
    - "/"
    - pipeline
    - apps
    - Nuke.*
    expression:
    - Nuke\d.+
    version_expression: Nuke(?P<version>.*)\/.+$
    launch_arguments:
    - "--studio"
  windows:
    prefix:
    - P:\
    - apps
    expression:
    - Nuke.*
    - Nuke\d.+.exe
    version_expression: "(?P<version>[\\d.]+[vabc]+[\\dvabc.]*)"
    launch_arguments:
    - "--studio"
  darwin:
    prefix:
    - "/"
    - Volumes
    - pipeline
    - apps
    expression:
    - Nuke.*
    - NukeStudio\d[\w.]+.app

Then restart Connect to have it pick up the override - loading this launch config and merging it on top (first level dictionary merge) of the shipped Nuke Studio launch config extension.

In the Framework section, extensions are described more in detail and you will find examples on how to customise and extend the DCC integrations by adding extensions to their launch configs.