DIGIT Public Finance Management
PlatformDomainsAcademyDesign SystemFeedback
v2.0
v2.0
  • Introducing Public Finance Management (iFIX)
  • Platform
    • Release Notes
      • iFIX Core Release Notes
        • iFIX Core Build Updates
        • iFIX Core Test Cases
      • iFIX Adaptor Release Notes
        • iFIX Adaptor Build Update
        • iFIX Adaptor Test Cases
    • Specification
      • Functional Specifications
      • Technical Specification
        • Information Model
        • APIs
    • Architecture
      • Technology
    • Services
    • Setup
      • iFIX Service Setup
      • Infrastructure Setup
        • Quickstart/Local Setup
        • On AWS
        • On Azure
      • Deploy Services
        • Deploy from your local machine
        • CI/CD
      • API Access Key
    • Configuration
      • Core Service Documents
        • Master Data Setup
          • Domain Services
            • iFIX Core Master Data Service
            • iFIX Core Fiscal Event Service
            • iFIX Core Fiscal Event Post-Processor
        • iFIX Core Data Cleanup
        • iFix Department Entity Service
        • iFix Client Management Service
          • Keycloak Setup
      • Configuring Master Data
      • Promotion Docs
        • Master Data Service Promotion Doc
        • mGramSeva iFIX Adapter
        • Department Entity Service Promotion
        • Fiscal Event And Fiscal Event Post-processor Service Promotion
        • MongoDB Migration
  • Products
    • Use Cases
      • Leveraging iFIX To Enable Timely Payments To Frontline Health Workers
    • Works Module
    • mGramSeva
    • iFIX Adapter
      • Adapter Service Documents
        • iFIX Adapter Master Data Setup
        • mGramSeva iFIX Adapter Service
        • iFIX Adapter Master Data Service
        • iFix Adapter Services
      • Source Code
      • Installation
        • Local Setup
        • CI/CD
    • iFIX Dashboard
      • Features
      • Architecture
        • Technology
      • Source Code
      • Installation
        • Local Setup
        • CI/CD
      • Documents
        • iFIX Reference Dashboard
          • iFIX Fiscal Event Aggregator
  • Community
    • Ecosystem
      • News and Events
    • Roadmap
    • PFM Blogs
      • Why PFM Needs Fiscal Information Exchange Standards
    • Source Code
    • 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?

  1. Products
  2. iFIX Adapter
  3. Installation

Local Setup

iFix Adapter

PreviousInstallationNextCI/CD

Last updated 3 years ago

Was this helpful?

The 2 Stages

Essentially, there are 2 stages that 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_Adapter_setup deployment script and simply answer the questions that it asks.

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

go run ifix_adapter_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.

All content on this page by is licensed under a .

repo
sops
env.yaml
​
eGov Foundation
Creative Commons Attribution 4.0 International License
Creative Commons License