# Keeping pipeline configurations current among various projects

**URL:** <https://community.shotgridsoftware.com/t/keeping-pipeline-configurations-current-among-various-projects/12400>\
**Category:** Pipeline Integrations\
**Created:** [May 13, 2021, 11:58pm UTC](https://community.shotgridsoftware.com/t/keeping-pipeline-configurations-current-among-various-projects/12400 "2021-05-13T23:58:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mmoshev](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/mmoshev/32/476_2.png) [@mmoshev](https://community.shotgridsoftware.com/u/mmoshev)\
**Post date:** [May 14, 2021, 9:22am UTC](https://community.shotgridsoftware.com/t/keeping-pipeline-configurations-current-among-various-projects/12400/2 "2021-05-14T09:22:14Z")

</div>

Hi, we also use git for managing our configurations. `core` is the main part of toolkit; there are several other modules. `tk-core` if I understand correctly is the package of all that, which gets cloned to each local centralized project’s directory and gets loaded from there for the project.  
This is basically toolkit.

We have a central location - a bare git repo - for the tk configuration, from which everyone else pulls. Something can be changed in one project, and pushed to the central repo, from which e.g. other projects can pull, new projects can clone.

For new projects, if your central config git repo is up to date, they will automatically be the latest version. In the Shotgun destkop wizard, for config source select “git”, and point it to your central repo. This clones the config. The project dir also contains core, under `install/core/python`.

The best workflow for updating I found is this - there is a test project, where I perform upgrades and test.  
You use the `tank` command:  
`tank updates` - for apps and engines  
`tank core` - for updating core

Then I commit the changes and pull to all other projects with a script.  
Finally, you have to run  
`tank cache_apps`  
in _each project_ to pull the apps that have been updated in the new configuration.  
This is easy with a bit of automation. The nice thing is you have a lot of control over each project.

This became a bit longwinded, and I cannot list all relevant info, so feel free to ask further questions.

Edit: [this recent thread](https://community.shotgridsoftware.com/t/recommended-way-to-share-update-pipeline-configurations-between-projects/5609/11) is relevant

---

_[View the full topic](https://community.shotgridsoftware.com/t/keeping-pipeline-configurations-current-among-various-projects/12400)._