# Source Control for Ignition

**URL:** <https://forum.inductiveautomation.com/t/source-control-for-ignition/19304>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [August 17, 2018, 1:45pm UTC](https://forum.inductiveautomation.com/t/source-control-for-ignition/19304 "2018-08-17T13:45:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![MattUlmer](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mattulmer/32/8736_2.png) [@MattUlmer](https://forum.inductiveautomation.com/u/MattUlmer)\
**Post date:** [May 23, 2019, 10:02pm UTC](https://forum.inductiveautomation.com/t/source-control-for-ignition/19304/3 "2019-05-23T22:02:35Z")

</div>

I would like to give this post a bump, so to speak, and see where things are at too. There was this statement a few years back, but my quick searches are not bringing anything forward:

> [@Any progress on version control system for Ignition?](https://forum.inductiveautomation.com/t/any-progress-on-version-control-system-for-ignition/15333/2):
>
> this is definitely on our minds as we work on Ignition 8

If there is no integration with 3rd party source control, what is the recommended way of controlling a project's source outside of the simple backup before starting changes and again before deployment, with possible Development/Stage/Production servers in place?

Thank you,

Matt

---

_[View the full topic](https://forum.inductiveautomation.com/t/source-control-for-ignition/19304)._
