-
Notifications
You must be signed in to change notification settings - Fork 450
Deploying the Functions runtime as a private site extension
David Ebbo edited this page May 2, 2016
·
24 revisions
If you already have a Functions app, you can use the following steps to deploy your own Functions runtime as a private site extension:
- In VS, right click the WebJobs.Script.WebHost project and choose Publish
- Select the existing File System profile and click Publish. This will create the bits under
src\WebJobs.Script.WebHost\Publish
- Go to the Kudu Console for the function app that you want to use your bits on
- Drag and drop the SiteExtensions folder from your machine (in
src\WebJobs.Script.WebHost\Publish
), into the root of your Kudu Console. i.e. this should created:\home\SiteExtensions\Functions
- In the Kudu Process Explorer, kill the main site (the w3wp that doesn't say
scm
)
You are now using your private Functions runtime.
- 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]