> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/build-and-deploy/local-setup.md).

# Local Setup

## Inji Verify Local Setup

This guide is designed to help users set up Inji Verify in their local environment, providing detailed instructions to replicate the platform's functionality on their machine for development or testing purposes.

#### **Repositories**

Clone the repositories in the local to bring up your setup. Repository information can be fetched from [**here**](https://github.com/mosip/inji-verify/blob/release-0.12.x/README.md#inji-verify)

#### **Installations**

Prerequisites: Node 18 - Can be installed using [**nvm**](https://github.com/nvm-sh/nvm)**.** Run the following commands to install the node

```
$ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
$ nvm install 18
```

* **JAVA 21**

  Can be installed using [sdkman](https://sdkman.io/). Run following commands to install node

  ```
  $ curl -s "https://get.sdkman.io" | bash
  $ sdk install java 21.0.5-tem
  ```
* [Maven](https://maven.apache.org/install.html)

#### **Folder Structure**

* **Helm:** The folder contains helm charts required to deploy on K8S
* **verify-ui:** This folder contains the source code for Inji Verify UI
* **verify-service:** This folder contains the source code for Inji Verify Backend Service
* **inji-verify-sdk :** This folder contains source code for Inji Verify SDK - which provided react components for Inji Verify UI integration.

Click on the [**ReadMe file**](https://github.com/mosip/inji-verify/blob/release-0.12.x/README.md#inji-verify) to explore more!

#### **Docker Compose**

Docker Compose provides two types of setup options: one for **developer setup**, enabling full-featured access for development and testing, and another for **demo setup**, optimized for showcasing specific use cases with simplified configuration.

**Developer Setup**

* To set it up for the developer, follow the steps outlined in the [**README**](https://github.com/mosip/inji-verify/blob/release-0.11.x/README.md#developer-setup) file for configuring Docker Compose for development, including necessary dependencies and configurations.

**Demo Setup**

* To set up the application on your local system for specific use cases or demo purposes, follow the steps provided in the [**README**](https://github.com/mosip/inji-verify/blob/release-0.11.x/README.md#demo-setup) file. The [**README**](https://github.com/mosip/inji-verify/blob/release-0.11.x/README.md#demo-setup) contains detailed instructions tailored to your requirements for easy setup and deployment.
* **Refer to the README for Docker Compose Instructions**
  * Inside the Inji Verify project directory, you will find a [**README**](https://github.com/mosip/inji-verify?tab=readme-ov-file#installations) file. This file contains detailed steps for setting up the project using Docker Compose.
  * Review the steps under the "Docker Compose" section for instructions on how to build and run the containers.
* **Run Docker Compose**
  * Use Docker Compose to build and deploy the application.
* **Access the Application**
  * Once the build is complete, the application will be available to access via the configured endpoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inji.io/inji-verify/build-and-deploy/local-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.