The page provides detailed steps on how to deploy the MUKTASoft services.
Steps: Follow the visual map below and click on the step links to view the details.
Please refer to this link for the service builds used.
Helm charts for all MUKTASoft services are available here. To override the environment variables, please create a Helm environment chart like this for your DIGIT environment and customise the values.
Create Common Masters
Create IdFormat.json that will be used by egov-id-gen service.
Create StateInfo.json which will configure eligible languages for the tenant
Create tenants by following this doc.
Create sample boundary data. Refer to this document for more details
Create configs for -
Configure map-config for the tenant
Restart the MDMS server and restart the Zuul API gateway.
Note: Any modifications made to the configuration mentioned above will necessitate a restart of the MDMS server. Similarly, changes to the "action-test.json" and "roleactions.json" files will require a restart of the Zuul API gateway.
Refer to the section for a list of core services to be deployed.
Refer to the section for a list of Works platform services to be deployed.
Refer to the section for a list of MUKTASoft services to be deployed.
Find below the breakdown of the steps:
Step 1: Create a persister config for each backend service. The persister service will use these configurations.
Step 2: Create an indexer config for each backend service. The indexer service will use these configurations.
Step 3: Create workflow configuration for the defined business services.
Note: If you make any changes to the indexer and persister configurations, you will need to restart the indexer and persister services for the changes to take effect.
Create users following this document.
Upsert localisation following this document.
MDMS configuration is listed for each service.
Last updated
Was this helpful?
Was this helpful?
