Create a new deploy from the contents of a folder Deploys from the build settings found in the netlify.toml file, or settings from the API.
The following environment variables can be used to override configuration file lookups and prompts:
NETLIFY_AUTH_TOKEN
- an access token to use when authenticating commands. Keep this value private.NETLIFY_SITE_ID
- override any linked project in the current working directory.Lambda functions in the function folder can be in the following configurations for deployment:
functions/
└── nameOfGoFunction
Build binaries of your Go language functions into the functions folder as part of your build process.
Build dependency bundled Node.js lambda functions with tools like webpack or browserify into the function folder as part of your build process.
functions/
└── nameOfBundledNodeJSFunction.js
You can ship unbundled Node.js functions with the CLI, utilizing top level project dependencies, or a nested package.json. If you use nested dependencies, be sure to populate the nested node_modules as part of your build process before deploying using npm or yarn.
project/
├── functions
│ ├── functionName/
│ │ ├── functionName.js (Note the folder and the function name need to match)
│ │ ├── package.json
│ │ └── node_modules/
│ └── unbundledFunction.js
├── package.json
├── netlify.toml
└── node_modules/
Any mix of these configurations works as well.
Function entry points are determined by the file name and name of the folder they are in:
functions/
├── aFolderlessFunctionEntrypoint.js
└── functionName/
├── notTheEntryPoint.js
└── functionName.js
Support for package.json’s main field, and intrinsic index.js entrypoints are coming soon.
Usage
Flags
alias
(string) - Specifies the alias for deployment, the string at the beginning of the deploy subdomain. Useful for creating predictable deployment URLs. Avoid setting an alias string to the same value as a deployed branch. alias
doesn’t create a branch deploy and can’t be used in conjunction with the branch subdomain feature. Maximum 37 characters.context
(string) - Specify a deploy context for environment variables read during the build (”production”, ”deploy-preview”, ”branch-deploy”, ”dev”) or branch:your-branch
where your-branch
is the name of a branch (default: dev)dir
(string) - Specify a folder to deployfilter
(string) - For monorepos, specify the name of the application to run the command infunctions
(string) - Specify a functions folder to deployjson
(boolean) - Output deployment data as JSONmessage
(string) - A short message to include in the deploy logno-build
(boolean) - Do not run build command before deploying. Only use this if you have no need for a build or your project has already been built.open
(boolean) - Open project after deployprod-if-unlocked
(boolean) - Deploy to production if unlocked, create a draft otherwisedebug
(boolean) - Print debugging informationauth
(string) - Netlify auth token - can be used to run this command without logging inprod
(boolean) - Deploy to productionsite
(string) - A project name or ID to deploy toskip-functions-cache
(boolean) - Ignore any functions created as part of a previous build
or deploy
commands, forcing them to be bundled again as part of the deploymenttimeout
(string) - Timeout to wait for deployment to finishtrigger
(boolean) - Trigger a new build of your project on Netlify without uploading local filesExamples
netlify deploy
netlify deploy --site my-first-project
netlify deploy --no-build # Deploy without running a build first
netlify deploy --prod
netlify deploy --prod --open
netlify deploy --prod-if-unlocked
netlify deploy --message "A message with an $ENV_VAR"
netlify deploy --auth $NETLIFY_AUTH_TOKEN
netlify deploy --trigger
netlify deploy --context deploy-preview
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