UI build preparation details for central instance
This page offers comprehensive instructions on preparing the UI build for the central instance. Follow the steps outlined in the respective sections below to successfully configure this setup.
Code Path: egovernments/DIGIT-Dev
A global configuration file should be generated for each instance. Example: UAT instance s3 bucket file Path: https://s3.ap-south-1.amazonaws.com/egov-uat-assets/globalConfigs.js
Add the below content to this file.
In this file -
Change the “stateTenantId” value as per instance; in this instance, it should be ‘pg’.
Change the “finEnv” value based on the specific instance; in this instance, it should be ‘uat’.
Change the “footerBWLogoURL” value as per instance requirements; in this instance, it should be ‘'https://s3.ap-south-1.amazonaws.com/egov-uat-assets/digit-footer-bw.png'’ (this is s3 link for footer image).
Change the “footerLogoURL” value as per instance requirements; for this instance, it is ‘'https://s3.ap-south-1.amazonaws.com/egov-uat-assets/digit-footer.png'’ (this is the s3 link for footer image).
Modify the "digitHomeURL" according to the instance requirements; in this instance, it should be set to "Coming Soon."
Change the "assetS3Bucket" value based on the specific instance; in this case, it should be set as "pg-egov-assets."
To modify the Google Maps key, you should make the necessary changes in the "gmaps_api_key" field.
If the "centralInstanceEnabled" parameter is configured as "false," the default behaviour of the logic will be active in the UI. Conversely, if the "centralInstanceEnabled" parameter is configured as "true," the central instance logic will come into effect.
The DevOps team generates this file as part of the new instance creation process. Finally, the file path is incorporated into the environment folder within the DevOps repository. Example: DIGIT UI repo path: egovernments/DIGIT-DevOps UAT File Path: uat.yaml These details are essential for the creation of a new instance build.
Activate the modules by utilizing the MDMS configuration, toggling the parameters to either "true" or "false." MDMS file path of UAT: citymodule.json