> 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/releases/deploy-a-release.md).

# Deploy a Release

{% hint style="info" %}
Deploying a Release is currently a standardised process that is part of the [Under the Hood](/features/deployments/under-the-hood.md#default-deployment-pipeline).
{% endhint %}

## Guide

To trigger the Default Deployment Pipeline for a Deployment:

1. Go to Modules -> Environments
2. Select the desired Module from the list
3. Use the Config popover to specify settings for the Deployment Pipeline
4. Use the Deploy or Roll Back popover to trigger the Default Deployment Pipeline now, or schedule it for later.
5. Monitor the status of each step in the pipeline from the Migrations view

{% tabs %}
{% tab title="Config" %}

<figure><img src="/files/SuhTDn2CVSamxEg7dZsR" alt=""><figcaption><p>Specifying Settings for the Deployment</p></figcaption></figure>
{% endtab %}

{% tab title="Trigger Rollout" %}

<figure><img src="/files/CaqXXfdlJtPpPo0mpnKW" alt=""><figcaption><p>Deploying the latest Release on <code>main</code> to the <code>PROD</code> environment</p></figcaption></figure>
{% endtab %}

{% tab title="Migration Logs" %}

<figure><img src="/files/wBijqsEvksSz7y60raAU" alt=""><figcaption><p>Monitor Data Migration progress and logs from the Migrations view</p></figcaption></figure>
{% endtab %}
{% endtabs %}

## Video Tutorial

{% embed url="<https://vimeo.com/1038622585?share=copy#t=0>" %}
Deploying a Release
{% endembed %}

## Deployment Config

### Authentication

<table><thead><tr><th width="184">Name</th><th>Description</th></tr></thead><tbody><tr><td>Account</td><td>Account name for the Deployment,  if different from the Module.</td></tr><tr><td>Password</td><td>Password for the Deployment,  if different from the Module.</td></tr><tr><td>Encryption Key</td><td>Encryption key for the Deployment, if different from the Module.</td></tr></tbody></table>

### Options

<table><thead><tr><th width="183">Name</th><th>Description</th></tr></thead><tbody><tr><td>Ignore Value Lists</td><td>Uses custom value lists from the released Version instead of the Deployment.</td></tr><tr><td>Ignore Accounts</td><td>Uses the account names, passwords, and the encryption password from the released Version instead of the Deployment.</td></tr><tr><td>Ignore Fonts</td><td>Doesn't check the font mapping for field contents.</td></tr><tr><td>Rebuild Indexes</td><td>Rebuilds existing indexes during migration instead of copying them from the Deployment.</td></tr><tr><td>Reevaluate Stored Calculations</td><td><p>Causes all stored calculations to be reevaluated.</p><p><strong>Note:</strong> Calculated values are recomputed and the orginal values might change, especially if the calculation includes some of the Get functions, the Random function, or any external functions (because the data migration tool doesn’t load any plug-ins)</p></td></tr></tbody></table>

### Other

<table><thead><tr><th width="183">Name</th><th>Description</th></tr></thead><tbody><tr><td>Timeout</td><td>A timeout (in minutes) for the Data Migration process on the target server. Defaults to the Project's Default Migration Timeout (600 mins).</td></tr></tbody></table>

### Post Migration Script

<table data-full-width="false"><thead><tr><th width="186">Name</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Name of the script to be run after the data migration (beware of script name limitations in the FM OData API)</td></tr><tr><td>Parameter</td><td>Script parameter for the script</td></tr><tr><td>Type</td><td>Parameter type</td></tr></tbody></table>


---

# 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:

```
GET https://docs.devin.fm/guides/releases/deploy-a-release.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.