Revision Management Strategies in Ignition 8

Now that the internal revision management system is gone. What is the best strategy for managing revisions and backups of projects. My developers only have access to Ignition via the designer (rather than access to the filesystem on the Ignition servers) as I want to encourage users to make displays etc within their own level of control/access. (and you can do everything from the designer/web interface so why expose the server terminal to every user?)

GIT is our misc tool of choice but without access to the file system it is harder to facilitate this. And having to export the project each time is a right pain (it’s annoying enough having to support the legacy FTView projects on site in this way).

What is everyone using?

1 Like