-
Notifications
You must be signed in to change notification settings - Fork 441
Configuration Settings
Mathew Charles edited this page Aug 24, 2017
·
18 revisions
In addition to host level settings that are configurable via host.json, there are also various things that you can configure using App Settings, which you can find on the Configure page in the Azure portal. When running locally, these same settings can be configured via environment variables.
- AzureWebJobsDisableHomepage - set to "true" to disable the default landing page shown for the root of the Azure Functions site
-
FUNCTIONS_EXTENSION_VERSION - this setting contains the version specifier governing the version of the Azure Functions runtime will be used. The default is
~1
which means always run with the latest version of the specified major version (in this case 1). This can also be set to a version string to pin the app to specific version (e.g. 1.0.12345). - AzureWebJobs_TypeScriptPath - path to the compiler used for TypeScript. This allows you to override the default if you need to.
- AzureWebJobsDotNetReleaseCompilation - specifies whether to use Release mode when compiling .NET code. The default is Release mode. Set to "false" to force debug compilation.
- AzureWebJobsScriptRoot - specifies the path to the root directory where Functions live (i.e. where the host.json and individual function folders live). When running in Azure, will default to "site\wwwroot".
- Configuration Settings
- function.json
- host.json
- host.json (v2)
- Http Functions
- Function Runtime Versioning
- Official Functions developers guide
- Host Health Monitor
- Managing Connections
- Renaming a Function
- Retrieving information about the currently running function
- Site Extension Resolution
- Linux Consumption Regions
- Using LinuxFxVersion for Linux Function apps
- Out-of-proc Cancellation Tokens
- Assembly Resolution in Azure Functions
- ILogger
- Precompiled functions
- Official Functions C# developer reference
- Contributor Onboarding
- Development Process
- Deploying the Functions runtime as a private site extension
- Authoring & Testing Language Extensions
- Bindings in out-of-proc
- Language Extensibility
- Worker Capabilities
- Investigating and reporting issues with timer triggered functions not firing
- Sharing Your Function App name privately
- Azure Functions CLI release notes [moved here]
- Function App Zipped Deployment [deprecated]