> For the complete documentation index, see [llms.txt](https://docs.devin.fm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devin.fm/guides/deployment-environments/connect-a-deployment.md).

# Connect a Deployment

{% hint style="info" %}
To setup a Deployment Environment for a Module, you must first add the server hosting it. See [Add a Server](/guides/servers/add-a-server.md).
{% endhint %}

## Guide

Then:

1. Go to Modules -> Environments
2. Select the desired Module from the list
3. Click Connect File and select the hosted file that you want to connect
4. Specifcy a Release Branch for the Deployment
5. Specify a version number for the Deployment

## Video Tutorial

{% embed url="<https://vimeo.com/938631001?share=copy>" %}
Connecting a `PRODUCTION` deployment (live hosted file) for each Module
{% endembed %}

{% hint style="info" %}
In Devin 1.1, Deployments are now Environments where deployed instances of a `fmp12` file  are linked to specific Release Branches. This allows you to specify custom deployment flows. For instance, you could link your `main` branch to your `production` server and a `test` branch to your `UAT/staging` server.
{% endhint %}


---

# 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.devin.fm/guides/deployment-environments/connect-a-deployment.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.