# Ignition development git best practice with multiple programmers

**URL:** <https://forum.inductiveautomation.com/t/ignition-development-git-best-practice-with-multiple-programmers/89349>\
**Category:** Ignition\
**Tags:** vision, perspective\
**Created:** [April 24, 2024, 11:27am UTC](https://forum.inductiveautomation.com/t/ignition-development-git-best-practice-with-multiple-programmers/89349 "2024-04-24T11:27:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emile\_Laplante](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@Emile\_Laplante](https://forum.inductiveautomation.com/u/Emile_Laplante)\
**Post date:** [April 24, 2024, 11:27am UTC](https://forum.inductiveautomation.com/t/ignition-development-git-best-practice-with-multiple-programmers/89349/1 "2024-04-24T11:27:23Z")

</div>

Hi,

I'm trying to setup the best workflow on an Ignition project with multiple programmers.

I have a mcu firmware developpement background so I'm used to work on a git repo where the project is cloned on our local machine and we make the development in an IDE.

I've read the following paper :

> **[Ignition 8 Deployment Best Practices](https://inductiveautomation.com/resources/article/ignition-8-deployment-best-practices)**
>
> Inductive Automation provides this helpful guide for deploying Ignition applications. The guide offers Ignition 8 best practices for setting up development and testing workflow.

But I don't understand the workflow with multiple programers since the projets files need to be stored in the folder /project on the gateway server.

Right now we have a server with a VM that is the gatweay on wich we all work.

I understand that with the binaires (we are working on vision) a typical worflow with branches and merges might not be possible. But being able to snap shot the project in time with comments, knowing who did the commit, being able to roll back to older version would help for the project development.

Do you have any suggestion on a Ignition developpment environnement with multiple programmers?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 24, 2024, 11:47am UTC](https://forum.inductiveautomation.com/t/ignition-development-git-best-practice-with-multiple-programmers/89349/2 "2024-04-24T11:47:30Z")

</div>

You will all need your own VM, plus the "master" VM.

Branches should be fine, but merges that involve the same resources will be ugly (and require touchups to resource.json hashes).

---

<div class="post-metadata">

**Author:** ![Emile\_Laplante](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@Emile\_Laplante](https://forum.inductiveautomation.com/u/Emile_Laplante)\
**Post date:** [April 26, 2024, 2:22am UTC](https://forum.inductiveautomation.com/t/ignition-development-git-best-practice-with-multiple-programmers/89349/3 "2024-04-26T02:22:55Z")

</div>

Thanks @pturmel !

Do you have any link to provide that could help me to set that up?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 26, 2024, 11:47am UTC](https://forum.inductiveautomation.com/t/ignition-development-git-best-practice-with-multiple-programmers/89349/4 "2024-04-26T11:47:11Z")

</div>

Sorry, no. I use git a great deal for module development, but not for Ignition itself.