> For the complete documentation index, see [llms.txt](https://promet-source.gitbook.io/provus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://promet-source.gitbook.io/provus/getting-started/installation.md).

# Installation

Welcome to the installation guide for Provus, a Drupal Kickstarter project. This guide will walk you through the steps to set up Provus on your local machine using various installation options. 

Installation guides include the required prerequisites and commands necessary to get Provus up and running.

During installation, you will have the option to install all or some of the included Provus modules. Descriptions of the functionality these Provus modules provide are located here for your reference: [Provus Modules](/provus/getting-started/installation/provus-modules.md)

{% content-ref url="/pages/369G6ciZAEFiWbFT9WIe" %}
[Using Docksal](/provus/getting-started/installation/using-docksal.md)
{% endcontent-ref %}

{% content-ref url="/pages/trSoMeyspHn1XFfaxCEv" %}
[Using Lando](/provus/getting-started/installation/using-lando.md)
{% endcontent-ref %}

{% content-ref url="/pages/TQpWL9HqHW5ANTrRMCPO" %}
[Using DDEV](/provus/getting-started/installation/using-ddev.md)
{% endcontent-ref %}


---

# 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://promet-source.gitbook.io/provus/getting-started/installation.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.