Create Deployments
Last updated
Last updated
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
manual deployment
automatic deployment through GitHub
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.
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.
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.
Like the manual deployment we have production and preview deployments through GitHub automatically upon PR creation.
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.
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.
After it’s built, you can view the preview URL right in the PR.
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.
