> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/developer-guide/backend-developer-guide/section-0-prep/development-pre-requisites.md).

# Development Pre-requisites

## Checklist

Before starting development on top of DIGIT make sure:

* [x] To check out the [Development Pre-requisites Training Resources ](/platform/guides/developer-guide/pre-requisites-training-resources.md#backend-pre-requisites-tutorials)page to learn how to deploy the required tools.
* [x] DIGIT code from DIGIT-OSS, egov-mdms-data, configs etc.. has been forked from GitHub under your organization’s umbrella account.
* [x] You have access to the forked repositories from your GitHub user account. Note that the user account is different from the organization's account.
* [x] Access a DIGIT environment - FQDN, Access keys etc..The DIGIT environment can be a single VM setup for a development environment. Please refer to these docs for the installation of DIGIT.
* [x] Install DIGIT in a development environment (Single VM setup) by following the [quick setup guide](https://core.digit.org/guides/installation-guide/quick-setup).
* [x] It is recommended to deploy the following services in the development environment -
  * [User](/platform/platform/core-services/user.md)
  * [MDMS](/platform/platform/core-services/mdms-v2-master-data-management-service/mdms-master-data-management-service.md)
  * [Localization](/platform/platform/core-services/location.md)
  * [Id-Gen](/platform/platform/core-services/id-generation-service.md)
  * [URL-shortener](/platform/platform/core-services/url-shortening-service.md)
  * [Workflow](/platform/platform/core-services/workflow.md)

Some of the above services can also be port-forwarded using Kubernetes to bypass user authentication.

* [x] Make sure the following DIGIT services are running in the local environment:
  * [Persister](/platform/platform/core-services/persister-service.md)
  * [Indexer ](/platform/platform/core-services/indexer-service.md)(optional)
  * [PDF Service](/platform/platform/core-services/pdf-generation-service.md)
* [x] [CD/CI](/platform/guides/installation-guide/infrastructure-setup/ci-cd-set-up.md) has been set up for DIGIT. This is a pre-requisite to deploying new DIGIT modules. CD/CI processes will be used to build and deploy the new module that will be developed.
* [x] [Design phase artefacts](/platform/guides/developer-guide/backend-developer-guide/section-0-prep/design-inputs.md)
* [x] In addition, knowledge of the following technologies is required for developing on DIGIT: (Refer to the [DIGIT Pre-requisites tutorials](#digit-pre-requisites-tutorials) for help with installing and deploying these tools)
  * Java/J2EE
  * Spring Boot
  * REST APIs and related concepts like path parameters, headers, JSON etc.
  * Git
  * PostgreSQL
  * Kafka


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/platform/guides/developer-guide/backend-developer-guide/section-0-prep/development-pre-requisites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.