# Create Deployments

So your app was deployed upon initial creation. We automatically assigned a “production” URL for you which looks something like <https://honeysuckle-aloe-tgsrtj6.dappling.network/>. Each deployment will also create a similar looking “preview” domain.

There are two ways we deploy your app

1. manual deployment
2. automatic deployment through GitHub

### Manual Deployment

If you navigate to the deployments tab of your project, you’ll see two buttons to deploy your app manually. There is a preview and production build option.

<figure><img src="/files/VkH74Mu8bFPqDi3Ofukg" alt=""><figcaption></figcaption></figure>

#### Production

On every “production” deployment, we will take your configured production branch (see the settings tab) and create a build. After the build is complete, we will assign both

* your production URL, which never changes through the life of the project
* your configured domains (see the domains tab)

For example, if you configured a domain at <https://ipfs.example.com>, after a successful production deployment, your users will see the new code at the <https://ipfs.example.com> domain.

#### Preview

For each preview build, we go through the same build process as well as using the production branch, but the production domain as well as the configured domains in the domains tab are not updated. instead, we create a newly generated preview url that looks like <https://chive-lily-zfiuy3b.dappling.network> This preview URL will never be updated again.

<figure><img src="/files/mpAdUja41WgPbaKHXFN5" alt=""><figcaption></figcaption></figure>

#### Project page while deploying

<figure><img src="/files/eGgJHI3frircO0kCIK3P" alt=""><figcaption></figcaption></figure>

#### Deployment page while deploying

<figure><img src="/files/ONsM3WCb4AOMbnrMxAAN" alt=""><figcaption></figcaption></figure>

### GitHub Deployment

Like the manual deployment we have production and preview deployments through GitHub automatically upon PR creation.

#### Production

On any push to “main” including when a PR is merged into main, a production deployment is kicked off. You can see this in the project’s deployments.

<figure><img src="/files/iNnqb8AwaObEVSbCq1jo" alt=""><figcaption></figcaption></figure>

#### Preview

When a PR is created and any subsequent pushes to the PR, a preview build is created. This preview build is visible in your project’s deployments as well. It will notify you that it is building first.

<figure><img src="/files/JdRj0ZXH2ZzxKttfZHyP" alt=""><figcaption></figcaption></figure>

After it’s built, you can view the preview URL right in the PR.

<figure><img src="/files/if9SZjVBYeDocBeH6NfR" alt=""><figcaption></figcaption></figure>

:cactus:*Fun Fact: The world's largest flower, Rafflesia arnoldii, can grow to nearly 3 feet in diameter. Ironically, it has a scent akin to rotting flesh.*


---

# Agent Instructions: 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.dappling.network/legacy-docs/getting-started/create-deployments.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.