# Reading tk-multi-publish2.yml (et all) from somewhere else? **URL:** \ **Category:** Pipeline Integrations\ **Created:** [January 27, 2020, 11:06am UTC](https://community.shotgridsoftware.com/t/reading-tk-multi-publish2-yml-et-all-from-somewhere-else/6449 "2020-01-27T11:06:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![philip.scadding](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/philip.scadding/32/30_2.png) [@philip.scadding](https://community.shotgridsoftware.com/u/philip.scadding)\ **Post date:** [January 27, 2020, 11:13am UTC](https://community.shotgridsoftware.com/t/reading-tk-multi-publish2-yml-et-all-from-somewhere-else/6449/2 "2020-01-27T11:13:50Z")
Hey! This sounds similar to your other question: > [@Recommended way to share/update pipeline configurations between projects?](https://community.shotgridsoftware.com/t/recommended-way-to-share-update-pipeline-configurations-between-projects/5609/6): > > 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](https://developer.shotgunsoftware.com/tk-core/initializing.html#distributed-configurations). 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… As the includes can be resolved with an environment variable, you could set it to point anywhere you like, not just the same config (I’m pretty sure it doesn’t need to be a relative path). So you could have a central location for your settings and point to that. --- _[View the full topic](https://community.shotgridsoftware.com/t/reading-tk-multi-publish2-yml-et-all-from-somewhere-else/6449)._