# "Installation" version control together with "Project" version control

**URL:** https://discourse.nodered.org/t/installation-version-control-together-with-project-version-control/18716
**Category:** General
**Created:** [2 December 2019 23:29 UTC](https://discourse.nodered.org/t/installation-version-control-together-with-project-version-control/18716 "2019-12-02T23:29:43Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![amodelbello](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/amodelbello/32/14668_2.png) [@amodelbello](https://discourse.nodered.org/u/amodelbello)
#### Post date: [2 December 2019 23:29 UTC](https://discourse.nodered.org/t/installation-version-control-together-with-project-version-control/18716/1 "2019-12-02T23:29:43Z")

</div>

The multi-project feature with version control is super awesome but I haven't been able to figure out how to get it to work inside a Node-Red installation that is itself in a git repository.

I have a git repo with custom nodes, community nodes, theming, etc and when I clone the repo, the projects directory is empty because each project is its own repo with its own .git directory.

Is there a best practice to structure a node red install in version control that uses projects? I was thinking maybe submodules but wanted to see if anyone else has come up with something better.