> For the complete documentation index, see [llms.txt](https://docs.taskforce.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskforce.sh/on-premises/docker/docker-compose.md).

# Docker compose

In order to facilitate the initial installation of the dashboard, please refer to this compose file that you can run locally to check that everything is running, just note that if you run the containers in localhost, you will need to configure [Auth0](/on-premises/aws/configure-your-instance/configure-auth0.md) accordingly.

```yaml
services:
  backend:
    image: docker.taskforce.sh/onprem/dashboard:1.0.0
    restart: always
    ports:
      - "9876:9876"
    environment:
      LICENSE_KEY: ${LICENSE_KEY}
      HOST: ${HOST}
      POSTGRES_HOST: postgres
      POSTGRES_PASSWD: ${POSTGRES_PASSWORD}
      POSTGRES_DB: ${POSTGRES_DB}
      AUTH0_CLIENTID: ${AUTH0_CLIENTID}
      AUTH0_DOMAIN: ${AUTH0_DOMAIN}
      AUTH0_AUDIENCE: ${AUTH0_AUDIENCE}
      REDIS_URL: redis://redis:6379
      MAILGUN_DOMAIN: ${MAILGUN_DOMAIN}
      MAILGUN_API_KEY: ${MAILGUN_API_KEY}

  postgres:
    image: postgres:latest
    expose:
      - "5432"
    restart: always
    ports:
      - "5432:5432"
    environment:
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_DB: ${POSTGRES_DB}

  redis:
    image: redis:latest
    restart: always
    ports:
      - "6379:6379"

```

As soon as the instance is up and running, you could try to use the [taskforce-connector](/on-premises/using-the-taskforce-connector.md) to expose the Redis instance that is running in docker to your Taskforce.sh instance. Then you should be able to see the "[monitoring](/on-premises/aws/monitors.md)" queue that handles the monitor checks and alerts for the rest of your connections. 


---

# 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.taskforce.sh/on-premises/docker/docker-compose.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.