Skip to content

Infosys/mimoto

 
 

Repository files navigation

Maven Package upon a push Quality Gate Status

mimoto

Overview

This repository contains source code for backend service of Inji Mobile and Inji Web. The modules exposes API endpoints.

Build & run (for developers)

The project requires JDK 21

without docker-compose Build & install

  1. Navigate to Utilities file, uncomment the constructor at Line# 81
  2. build the jar
    mvn clean install -Dgpg.skip=true -Dmaven.javadoc.skip=true -DskipTests=true
  1. Run following command
    mvn spring-boot:run -Dspring.profiles.active=local

with docker-compose

  1. To simplify running mimoto in local for developers we have added Docker Compose Setup. This docker-compose includes mimoto service and nginx service to server static data.
  2. Follow the below steps to use custom build image in docker-compose
  • Build the mimoto.jar mvn clean install -Dgpg.skip=true -Dmaven.javadoc.skip=true -DskipTests=true
  • Build docker image, use any image tag docker build -t <image-with-tag> .
  • Use newly built docker image in docker-compose file

Deployment

Install

  1. Execute inji-config-server install script
cd helm/inji-config-server
./install.sh
  • Review values.yaml and make sure git repository parameters are as per your installation.
  1. Execute Onboarder install script
cd partner-onboarder
./install.sh
  • During the execution of the install.sh script, a prompt appears requesting information for the S3 bucket, including its name and URL.
  • Once the job is completed, log in to S3 and check the reports. There should not be any failures.
  1. Execute mimoto install script
cd helm/mimoto
./install.sh
  • During the execution of the install.sh script, a prompt appears requesting information regarding the presence of a public domain and a valid SSL certificate on the server.
  • If the server lacks a public domain and a valid SSL certificate, it is advisable to select the n option. Opting it will enable the init-container with an emptyDir volume and include it in the deployment process.
  • The init-container will proceed to download the server's self-signed SSL certificate and mount it to the specified location within the container's Java keystore (i.e., cacerts) file.
  • This particular functionality caters to scenarios where the script needs to be employed on a server utilizing self-signed SSL certificates.

For Onboarding new Issuer for VCI:

  • create a folder "certs" in the root and a file "oidckeystore.p12" inside certs and store the keys as different aliases for every issuers. for more details refer here

Credits

Credits listed here

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Java 87.3%
  • HTML 6.5%
  • Shell 3.2%
  • Handlebars 1.7%
  • Dockerfile 0.9%
  • Smarty 0.3%
  • Python 0.1%