# Enable/Disable Project Through Scripting **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [October 12, 2021, 11:52pm UTC](https://forum.inductiveautomation.com/t/enable-disable-project-through-scripting/51875 "2021-10-12T23:52:08Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![williamsr.andrew](https://avatars.discourse-cdn.com/v4/letter/w/df705f/32.png) [@williamsr.andrew](https://forum.inductiveautomation.com/u/williamsr.andrew)\ **Post date:** [January 30, 2022, 3:22am UTC](https://forum.inductiveautomation.com/t/enable-disable-project-through-scripting/51875/3 "2022-01-30T03:22:36Z")
Thanks @dustin.cooper! I’m glad this was able to help you! I haven’t really looked into the project change tracking that you are talking about, but it does look like `RuntimeProject` should be able to do something like this. The `diff` function looks like it _should_ do what you want, you would just need to compare the `prod` version of the project to the updated `dev` version. Right now I am just tracking changes manually. Each of my projects has a `version` Project Script where I keep a handful of variables like author, last modified date, and a changelog dictionary. Obviously it becomes an issue if you forget to update this, but I figure its better than nothing. You could then either import the file to access those variables, or read in the file and search for those variables. This discussion has sparked me to look into using git for project change/version control, and it looks like there has been quite a bit of discussion around it already. If you really want to be more rigorous in change management, this would definitely be something to look into further: > [@Best Practices for SVN/GIT on projects](https://forum.inductiveautomation.com/t/best-practices-for-svn-git-on-projects/30218): > > I am now experimenting with keeping my data/projects directory as a git repository, similar to described in [this thread](http://forum.inductiveautomation.com/t/svn-compatibility/28747). It’s still a bit of a bumpy process, but it definitely feels more precise (i.e. safe) than the prior methods of maintaining project history. One question I’m still trying to figure out is if there are any sub-directories or files that we should add to the .gitignore files. At the moment, I’m suspicious of the conversion-report.txt file and the .resources directory. Can any… Here’s are a couple of resources that might be interesting for monitoring/tracking project changes: [https://docs.inductiveautomation.com/display/SE/Working+with+Project+Resources](https://docs.inductiveautomation.com/display/SE/Working+with+Project+Resources) > **[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. --- _[View the full topic](https://forum.inductiveautomation.com/t/enable-disable-project-through-scripting/51875)._