Tk-multi-publish2 show based setting

[ihwangj]

Hello,

What is the best way to handle show-based settings for tk-multi-publish2? For example, show A and show B use the default publish workflow while show C and has their own custom publish workflow?
It looks like with the current setup, I will need to create a different configuration for each show rather than maintain one configuration for all shows and allow different settings/template for each show.

Thanks,
Iris

[philip.scadding]

Hi Iris

That is correct, the normal approach would be to have a different config.
However it is possible to do a per project configuration in the same config, but it becomes more complicated. I suggest an approach here:

Recommended way to share/update pipeline configurations between projects?

I thought I’d chime in with a suggestion as well. Option 1 Another approach would be to have a site config (a PipelineConfiguration entity with no project set), using a distributed setup. This will mean that all projects that don’t have their own config will use the site config (you will still need to set a tank_name value on each Project entity).Then to take over for a specific project, you can just create a PipelineConfiguration for that project. That will be a full config take over though. O…

Best
Phil

[ihwangj]

Thank you, Phil. I read the post and it was really helpful!