This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 652
Home
David Ebbo edited this page Mar 24, 2015
·
114 revisions
Kudu is the engine behind git deployments in Azure Web Sites. It can also run outside of Azure.
- Post to the Azure Git Deployment forum on MSDN
- Go to the Kudu room on JabbR
- Ping @davidebbo, @suwat_ch, @pranav_km, @amitapl or @mtian on Twitter
If you are using git to push to an Azure Web Site, this is the section you'll care most about.
See the Version history page for details.
- Publishing a website from Source Control (official documentation from windowsazure.com)
- Deployment hooks: how to take over the deployment logic for a site
- Web Hooks
- Azure Site Extensions (see also Xdt Transform Samples)
- Post Deployment Action Hooks
- Web Jobs
- Accessing the Kudu service
- Customizing Deployments: choosing which folder or project to deploy to the web site
- Deployment branch: choosing the branch that gets deployed when you push
- Deploying from GitHub
- Managing settings and secrets: how to modify the values when the app is deployed
- Managing database connections in Azure Web Sites
- Accessing files via FTP
- Deploying inplace and without repository
- Using a custom web.config for Node apps
- Sending an email when your Azure web site deployment completes
- Kudu architecture
- REST API
- Enabling continuous deployment from Github, Codeplex and Bitbucket
- File structure on Azure
- Azure Runtime Environment
- Understanding deployment credentials
- How Kudu deploys sites
- Configurable settings
- Deployment Environment
- Known issues
- Investigating Issues
- Using the Kudu Console
- Diagnostic Log Stream
- Investigating Continuous Deployment
- Process Threads list and minidump/gcdump/diagsession
Read this is you are interested in contributing to Kudu