Help with tk-nuke bootstrap

tonyd · April 29, 2020, 10:07am

Hey folks,
I’m trying to wrap my head around the bootstrap logic of tk-nuke for all of the different nuke dcc’s. The goal is to separate the startup env vars for nuke and hiero in this engine for better differentiation.
The engine.py states that “tk-nuke/python/startup/bootstrap.py” is the first bit of logic that will be executed.
However in my case this is never executed as far as i can tell.

Can someone maybe shed some light on the bootup process for tk-nuke?

DavidMason · April 29, 2020, 10:25am

Hey @tonyd,

Check out this doc about bootstrapping;

github.com

shotgunsoftware/developer.shotgunsoftware.com/blob/master/docs/en/guides/pipeline-integrations/development/sgtk-developer-bootstrapping.md

---
layout: default
title: Bootstrapping and running an app
pagename: sgtk-developer-bootstrapping
lang: en
---

# Bootstrapping and running an app

This guide walks you through the process of initializing a Toolkit engine so that you can run custom code or launch apps, also known as bootstrapping.

Bootstrapping is useful in situations where a Toolkit engine has not already been started and you need to use the API.
For example, you might have a processing script that runs on a render farm and needs to utilize the Toolkit API to handle paths and context.
Or you may wish to be able to run your Toolkit app from your favorite IDE.

{% include info title="Note" content="If you are using a [distributed config](https://developer.shotgunsoftware.com/tk-core/initializing.html#distributed-configurations), a Toolkit engine must be initialized before running Toolkit API methods. It is possible to use the API without bootstrapping an engine if you are using a [centralized config](https://developer.shotgunsoftware.com/tk-core/initializing.html#centralized-configurations), using the [factory methods](https://developer.shotgunsoftware.com/tk-core/initializing.html#factory-methods), however, you will need to manually find the path to the correct core API for your project when importing `sgtk`." %}


### Requirements

This file has been truncated. show original

Should get you started on the topic, not sure if you’ve seen all of our documentation. Hopefully someone more versed in the subject can get into specifics

tonyd · April 29, 2020, 10:30am

Cool… haven’t found this one yet. Thanks David

DavidMason · April 29, 2020, 11:01am

Hi @tonyd,

Have you checked out the hooks before_app_launch.py or app_launch.py? might be a place to set those envars with logic there?

-David

tonyd · April 29, 2020, 2:22pm

briefly… I also thought to set NUKE_PATH and HIERO_PLUGIN_PATH to something that fits my needs from there.
But I wanted to understand where and how those variables are set by default and hook in from there

philip.scadding · April 29, 2020, 2:27pm

Hey @tonyd

tk-nuke sets those env vars in the startup.py, which gets called by the tk-multi-launchapp when launching Nuke. But I wouldn’t recomend taking over the engine to modify them here. As @DavidMason mentioned, setting them in the before_app_launch.py would be a better way to go I think.