> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.5/setup/3.-installation/3.1-set-up-a-development-environment.md).

# 4.1 Set-up a local development environment

{% hint style="warning" %}

### Important! Please read

The following instructions will guide you on how to set up a local, development environment of OpenCRVS, on your laptop, using our fictional country configuration: "Farajaland" for development and configuration purposes.  To learn how to deploy OpenCRVS to a server host, the documentation is at [3.3 Set-up a server-hosted environment.](/v1.5/setup/3.-installation/3.3-set-up-a-server-hosted-environment.md)
{% endhint %}

{% hint style="warning" %}
We recommend that you setup OpenCRVS on your local laptop to work with our fictional country repo before proceeding to fork and create your own country configuration.

In order to run OpenCRVS, we expect that you have a working knowledge of Linux / Unix operating systems and can run terminal commands.  You should also be familiar with Docker and NodeJS.
{% endhint %}

First, you will have to install some dependencies on your local computer.


---

# 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://documentation.opencrvs.org/v1.5/setup/3.-installation/3.1-set-up-a-development-environment.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.