Hello,
i am trying to make a clone environment for new devs to experiment. we are working on a brand new factory and the development is quite fast. So for now, i just want to use git to push one gw (dev) and second gw (crash) to pull the first.
for now i used guide https://docs.inductiveautomation.com/docs/8.3/tutorials/version-control-guide and i used .gitignore from there. i can succefully push to git repo, i can successfully pull at the secondary “crash” instance.
Problem 1: files to version control
i found that the .gitignore does not ignore ignition.conf. This file defines the Deployment mode, when I sync, without complex merging technique, it overwrites. Maybe, I have read i can use an env var in Docker container? But I cannot find such var. https://www.docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/platform-environment-variables#environment-variables
for now I added ignition.conf to .gitignore
Problem 2: again files to version control
After using the basic .gitignore, there I have around 10000 files in version control, we have around 150 views in 1 project. I think, that the .gitignore file in the git guide i not restrictive enough, that there loads of unneeded files.
I wouldn’t care, but later i will need to merge git branches, merge dev branch to crash branch and loads of unneeded files will cause merge issues.
Ref: https://docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/gateway-folder-structure
Overall view: We have dev gw connected to about 10 OPC servers, for tags, we use loopback OPC server. We have one Postgres DB for history and all.
Plan is to access dev’s gw OPC server from crash instance to have live data. The crash instance should use its own Postgres DB. This will be accomplished through GW Deployment modes.
I would be happy for any hints.
In future I would like to create classic pipeline dev-test-prod. But now I want to create an instance for experiments.