This page covers features and tools you can use to create deploys with or without continuous deployment.
Note
When you create a deploy manually without continuous deployment, Netlify does not run a build command.
Continuous deployment works by connecting a Git repository to a Netlify site and keeping the two in sync. This is done using the Git provider’s OAuth2 authentication or the Netlify GitHub App.
After you set up Git provider permissions and link a repository, Netlify will run your build command and deploy the result whenever you push to your Git repo. The benefits of Netlify’s continuous deployment include:
You can use the CLI to set up continuous deployment for a Git repository. Once continuous deployment is configured, you can update your Production site, staging site, or Deploy Preview with git push.
You can also use the CLI to create manual deploys without continuous deployment. For example, you can deploy directly to your production site from the command line with netlify deploy --prod.
Tip
For easiest deployment and management, make sure you’re already logged in to the team where you want your site project to be on Netlify.
You can create a new site by dragging a project folder containing your site files (like .html files) to Netlify Drop. You can also find a drag and drop section at the bottom of your team’s Projects page.
If you need to update a site that you created using drag and drop, update and rebuild your project locally. Then, drag the project’s updated output folder to the deploy dropzone at the bottom of the site’s Deploys page. This will start a new site deploy with the updated files. You can also use this functionality to manually update any site that is not connected to a Git repository.
You can use the API to create deploys manually using a file digest or a ZIP file.
The Deploy to Netlify button helps users deploy new sites from templates with one single click. Web developers can use the button to give their users a one-click way to deploy those applications on Netlify.
It’s designed to be used in README files, documentation sites, and probably anything that renders as an HTML file.
You can find examples of the button in use in the READMEs on our templates.
The template code must be available in a public repository stored on GitHub.com or GitLab.com.
You can use any markup language that renders as HTML to display the button. There are two very important URLs that you’ll need:
The SVG URL for the button: https://www.netlify.com/img/deploy/button.svg.
The URL the button takes users to: https://app.netlify.com/start/deploy. This link requires the public Git repository as a parameter, for example:
https://app.netlify.com/start/deploy?repository=https://github.com/netlify/netlify-statuskit
You can make the button clone a whole repository or just a portion of a repository. Both are good options for monorepos but you may need to set a base directory if the button clones the whole repository.
Here is an example of the full Markdown or HTML code for a Deploy to Netlify button that deploys the Netlify StatusKit template:
[](https://app.netlify.com/start/deploy?repository=https://github.com/netlify/netlify-statuskit)
<a href="https://app.netlify.com/start/deploy?repository=https://github.com/netlify/netlify-statuskit">
<img src="https://www.netlify.com/img/deploy/button.svg" alt="Deploy to Netlify">
</a>
If your repository uses extensions built with Netlify’s SDK, you can add the URL parameter fullConfiguration=true to make users go through an extra step where they’ll be able to install required extensions, choose a site name, and configure their new repository before deploying the site.
You can control some aspects of template configuration directly in the template’s Git repository.
Create a netlify.toml file in the root of the repository, if you don’t have it already. Netlify will read the information from there. If your Deploy to Netlify button clones just a subdirectory of the repository, create the netlify.toml file in that subdirectory so that the file ends up in the root of the cloned repository. This file can also be used to set options for continuous deployment, you can read more about it in the file-based configuration documentation.
Within the [template] section of the netlify.toml, you can set three directives:
A list of incoming hooks for the users site. This is very useful if you want to allow a third party service to control when to deploy the site. This is what headless CMS services like Contentful and DatoCMS do. Users can give those providers the address Netlify generates for their specific incoming requests.
[template]
incoming-hooks = ["Contentful"]
A list of required environment variables. This is one way to let users set specific configuration options upon deployment. It also enables customization without having to change the code of the base template. If you don’t want to use a netlify.toml file, you can instead use the URL hash to require or even pre-fill environment variables.
[template.environment]
SECRET_TOKEN = "change me for your secret token"
CUSTOM_LOGO = "set the url to your custom logo here"
The placeholder strings you set in netlify.toml are used as labels in the UI to provide guidance to users deploying your template.
A list of required extension slugs. Extensions expand the capabilities of a site deployed on Netlify. This is useful if you wish to specify your template depends on specific Netlify extensions to work as expected. If you define required-extensions, users will be prompted to install the extensions, to allow them to get up and running faster. This can be combined with the optional parameter fullConfiguration=true if you wish to force users to install the extension(s) prior to the first deploy of their site.
[template]
required-extensions = ["supabase"]
Note that you can’t do the following in this [template] section:
base query parameter instead.You can control the following aspects of how the template repo is cloned and how the resulting site is configured by passing values in the Deploy to Netlify URL:
You can require or set environment variables for the site template in the hash of the template’s Deploy to Netlify URL with key/value pairs. Values can be null.
https://app.netlify.com/start/deploy?repository=https://github.com/myworkspace/sweetkittentemplate#SECRET_TOKEN=specialuniquevalue&CUSTOM_LOGO=
Passing environment variable values in the hash ensures that they’re processed on the client side only. You can create custom Deploy to Netlify buttons for your users with tokens and other secure data, and they won’t appear in Netlify logs.
If your Deploy to Netlify button clones a whole monorepo rather than a single subdirectory, you can use the base query parameter to set an alternate directory as the base directory for deployments. The format is &base=your-base-directory. Note that while Netlify uses the specified base directory for the build and deploy, the entire repo is still cloned to the user’s Git provider account.
For example, here’s a URL with a base directory of blog:
https://app.netlify.com/start/deploy?repository=https://github.com/myworkspace/sweetkittentemplate&base=blog
When someone uses this Deploy to Netlify button, Netlify clones the whole sweetkittentemplate repository to the user’s Git provider account and then builds and deploys from the blog subdirectory.
Note the following limitations:
netlify.toml in the base directory will take precedence over the root level configuration for that site’s builds.To make a Deploy to Netlify button clone just a part of a repo, use the create_from_path query parameter to specify a subdirectory to clone. The format is &create_from_path=your-subdirectory.
For example, here’s a URL with a creation path of examples/hello:
https://app.netlify.com/start/deploy?repository=https://github.com/myworkspace/demos&create_from_path=examples/hello
When someone uses this Deploy to Netlify button, Netlify clones just the subdirectory examples/hello from the demos repo to the user’s Git provider account and then builds and deploys from the root of the cloned repository.
To make a Deploy to Netlify button deploy a branch other than the default branch, use the branch query parameter. The format is &branch=your-branch.
For example, here’s a URL that will deploy the beta-feature branch:
https://app.netlify.com/start/deploy?repository=https://github.com/myworkspace/app&branch=beta-feature
When someone uses this Deploy to Netlify button, Netlify sets the new site’s production branch to beta-feature and then builds and deploys from that branch of the cloned repository.
You can define additional configuration instructions in the USAGE.md file, which should be saved in the root of your repository. This can be useful to include guidance on setting up any required third-party service accounts (such as databases, content sources, analytics platforms, or APIs) and provisioning those services. Be sure to mention any necessary extensions or tools that need to be pre-installed to ensure a smooth setup.
When a USAGE.md file is included in the root of the repository, Netlify’s app will prompt users to read the additional instructions included in it during the fullConfiguration flow and, after the site has been deployed, in the site overview.
Build hooks give you unique URLs you can use to trigger new builds and deploys.
Netlify is available on Zapier, where you can connect Netlify with over 1,000 other applications. You can use Zapier “Zaps” to start a new deploy of your site in response to a trigger from another service. You can find out more on our blog, or use one of the templates below to get started:
Netlify is available on n8n, an open source tool that allows you to connect Netlify with other applications. By using one of n8n’s Netlify nodes, you can create your own automated workflow. To get started, you can use the Netlify node, Netlify Trigger node, or you can use the existing workflow below:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4