Azure Kudu Tools

The Azure website provides a good tool for analyzing our site------KUDU, let's see what this tool can do for us and when to use it.

How to open Kudu

The powerful features that Kudu has to show

How to open Kudu

1) Download the Publish configuration file

Open the Azure portal, select the Azure Web site, click Dashboard, download the release profile, such as:

2) access to the Kudu console

We need to add "SCM" to our Azure website address, for example, if your website is: http://example.chinacloudsites.cn/, we will use: https:// example.scm.chinacloudsites.cn/to access, then a pop-up window requires us to enter a username and password

3) In the first step, find username and userpwd into the second step of the pop-up window, so we can enter the Kudu tool

KUDU The powerful features that are presented

Environment

In the Environment page, you can view information about the environment in which the site is currently running. This includes general system information, application settings, environment variables, paths, HTTP headers, and server variables.

Debug Console

Here we introduce the most commonly used function "Debug console", we can choose cmd or PowerShell way to enter the corresponding console command interface

This console interface can do those things for us, I summed up the following points:

1) Uploading Files

By dragging the file directly into the area, a blue section appears, in which case we can upload the file.

Note: If we need to upload a folder, we need to compress it using the zip tool, then drag and drop the compressed file into the blue area, as far as I can test the direct drag folder is not effective.

2) Download/edit/delete files

The buttons in the Allow us to download the files, the folders are downloaded in zip packaging.

The buttons in the can let us directly edit the file, if we need to modify the configuration file, we do not need to re-modify the upload.

The buttons in the Help us to delete the file

3) View the integrity of the file

When we encounter "404 Not Found" error, we can check to see if the file exists.

4) View Log file

If we have logging enabled in the Azure portal settings, we can go directly to the corresponding log file via "Debug console", and for more information on enabling diagnostic logging for the Azure Web site, read:/http Www.windowsazure.cn/documentation/articles/web-sites-enable-diagnostic-log

5) Some command commands

RMDIR/S/q To quickly delete the folder and its sub-files.

echo%PATH% Gets the environment variables, and if there are git, Nodejs, NPM and so on in the environment variables, we can also perform the corresponding command operation.

Wait, wait.

Process Explorer

We can look at the details of our corresponding process through the "Process Explorer" interface, and if we are dealing with a request that "pid" has changed, we can judge that the crash of our program may have occurred.

Site Extensions

This feature can do some extensions for our website, for example, a tool used in PHP development, composer, when we install this extension, restart our site, again in the "Debug console" interface to see the following changes:

Note: If there are no changes after the installation is complete, try restarting the Web site on the Azure portal site and refreshing kudu.

We can see that the "siteextensions" is added to this folder and see the Composer.phar file in it, when we are in the "Environment" PATH (or enter echo%PATH% again We can also see that composer has been configured in the environment variables, that is, we can use composer in the Azure website to manage our PHP dependent library files, and of course there are many other extensions that we can use in the process of one by one attempts.

Azure Kudu Tools