DIGIT Docs
v2.4
  • DIGIT Knowledge Base
  • Local Governance
v2.4
  • 👋Introducing Public Finance Management (PFM)
    • Release Notes
      • Service Build Updates
      • MDMS & Configuration Updates
      • Test Cases
      • Data Migration
  • Understanding Public Finance
    • Public Finance Strategy & Approach
      • Approach Framework
    • Value Proposition
    • Potential Use Cases
  • Specifications
    • iFIX Specifications
      • Functional Specifications
  • Exemplars
    • PFM Implementations
      • Odisha
        • MUKTASoft
  • Technology
    • Design Approach
    • Tools
    • Architecture
      • High-Level Design
      • Low Level Design
        • DIGIT Exchange
        • Program Service
  • Setup
    • Install iFIX
      • Install Using GitHub Actions In AWS
    • Configuration
      • Configuring Master Data
      • Services
        • Program Service
        • DIGIT Exchange
        • MUKTA iFIX Adapter
    • Source Code
  • Community
    • Public Finance Blogs
      • Re-imagining Digital PFM in India
      • A Transformative Odyssey: The Impact of Smart Payments in Benefit Delivery
      • Why PFM Needs Fiscal Information Exchange Standards
      • News and Events
    • Ecosystem
      • Partner Engagement
    • Discussions
    • Issues
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page

Was this helpful?

Export as PDF
  1. Setup
  2. Integration
  3. iFIX Dashboard
  4. Installation

Local Setup

iFix Dashboard

Last updated 5 months ago

Was this helpful?

The 2 Stages

Essentially, 2 stages should allow you to use the full potential of DeploymentConfig and pipeline-as-code.

Stage 1: Clone the DevOps , choose your iFix product branch as iFix-adapter.‌

Prepare an <> master config file, you can name this file as you wish which will have the following configurations, this env file need to be in line with your cluster name.‌

  • each service global, local env variables

  • credentials, secrets (You need to encrypt using and create a <env>-secret.yaml separately)

  • Number of replicas/scale of individual services (Depending on whether dev or prod)

  • mdms, config repos (Master Data, ULB, Tenant details, Users, etc)

  • sms g/w, email g/w, payment g/w

  • GMap key (In case you are using Google Map services in your PGR, PT, TL, etc)

  • S3 Bucket for Filestore

  • URL/DNS on which the DIGIT will be exposed

  • SSL Certificate for the above URL

  • End-points configs (Internal/external)

Stage 2: Run the iFix_Dashboard_setup deployment script and simply answer the questions that it asks.

cd iFix-DevOps/deploy-as-code/egov-deployer

go run ifix_dashboard_setup.go

#Be prepared for the following questions
1. Do you have the Kubernetes Setup?
2. Provide the path of the intented env kubeconfig file
3. Which version of the DIGIT that you want to install
4. What mGramSeva Modules that you choose to install (Choose PGR)
5. All, done, Now do you want to preview the deployment manifests 
6. Are you good to proceed with the DIGIT Installation

All Done. Essentially, DIGIT deployment means that we need to generate Kubernetes manifests for each individual service. We use the tool called helm, which is an easy, effective and customizable packaging and deployment solution. So depending on where and which env you initiate the deployment there are 2 modes that you can deploy.

repo
sops
env.yaml