Frontend project architecture, farmework/production/development

Ignition
,
1

Hello,

I am planning to rebuild the main frontend project in the SCADA application.

I would like to get some advice on a few matters. The assumptions are:

  1. A main project from which other projects will inherit. This would serve as a framework for creating all other applications.
  2. A production project that will inherit components from the strictly managed framework.
  3. A development project for testing changes by several developers before they are introduced into production as custom or included within the framework.

All projects have access to the same tag providers, development does not affect them, and it is not possible to create a separate dev environment for tag providers for various reasons.

Based on my knowledge, what I have worked out could look like this:

       [ framework ]
            ↓
       [ common ]        ← everything that works and has passed tests
          ↙      ↘
[ production ]   [ dev ]

framework – common elements for all other projects, managed and inherited from a single place
common – an intermediate layer which will actually be the production project
production – a project only for running the production version
dev – a project for testing introduced functionalities

The intermediate common layer was intended to help me synchronize the development and production projects because both inherit from it. Changes tested in dev would be moved to common as custom for the production project and to the framework if they concerned all others.

However, I encountered a synchronization problem. The issue for me is the lack of inheritance of certain elements such as pages. Once a project is created from the parent project, it fetches pages but never updates them again. This severely disrupts my concept. I tried systematically copying the page.json configuration from the gateway server and injecting it into the projects to bypass synchronization, but these settings seem to be embedded internally and do not affect synchronization.

Are there workarounds for this or a better idea for a solution while maintaining such assumptions?

Best regards,
Michał Góralczyk

2

Inheritance is resource by resource, not any finer grain. Page configurations are one resources, similar to gateway events. Just don't plan on inheritance for such.