> 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/complaints-management/deploy/setup/single-machine-setup/docker-compose.md).

# Docker Compose

### Option A: Docker Compose Setup Steps

{% stepper %}
{% step %}

### Clone the repository

```
git clone https://github.com/egovernments/Citizen-Complaint-Resolution-System.git
cd Citizen-Complaint-Resolution-System/local-setup
```

{% endstep %}

{% step %}

### Start all services

The command below pulls \~20 container images and starts them. The first run takes 5-10 minutes to download images.

```
docker compose up -d
```

{% endstep %}

{% step %}

### Wait for services to become healthy

```
# Watch containers until all show "healthy" (~3-5 minutes after images are pulled)
watch 'docker compose ps --format "table {{.Name}}\t{{.Status}}" | grep -v "Exited"'
```

**What to expect**: You'll see containers transition from `starting` to `healthy` one by one. All containers (except `digit-ui` which may show `unhealthy` initially) should show `(healthy)` within 5 minutes.

**How to know it's ready**: When you see all services show `(healthy)`, press `Ctrl+C` to exit the watch. Then verify:

```
# Run the health check script to confirm all services are up
bash scripts/health-check.sh http://localhost
```

Expected output: each service prints `OK` or `healthy`.
{% endstep %}

{% step %}

### Access the application

**Login to the UI**:

1. Open <http://localhost:18000/digit-ui/employee>
2. Select city: **City A**
3. Username: `ADMIN`
4. Password: `eGov@123`

| What                      | URL                                               |
| ------------------------- | ------------------------------------------------- |
| DIGIT UI (Employee login) | <http://localhost:18000/digit-ui/employee>        |
| Kong Gateway (API base)   | [http://localhost:18000](http://localhost:18000/) |
| Gatus Health Dashboard    | [http://localhost:18889](http://localhost:18889/) |
| {% endstep %}             |                                                   |

{% step %}

### Stop the stack

```
docker compose down                        # Stop (preserves data for next time)
docker compose down -v --remove-orphans    # Stop and delete ALL data (clean slate)
```

{% endstep %}
{% endstepper %}


---

# 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.digit.org/complaints-management/deploy/setup/single-machine-setup/docker-compose.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.