Microsoft Azure Open Source Development Support Team Blog https://docs.microsoft.com/archive/blogs/azureossds/feed.xml Support for Open Source Technologies on Microsoft Azure App Service Tue, 28 May 2019 05:37:12 GMT en-US hourly 1 How to send emails through Azure Web Apps using Google / Gmail https://docs.microsoft.com/archive/blogs/azureossds/how-to-send-emails-through-azure-web-apps-using-google-gmail Sat, 02 Feb 2019 12:29:38 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5895 How to send emails through Azure Web Apps using Google / Gmail

Part I – Configuring Google to use App Passwords

  Two quick notes before proceeding: This is not a ‘once and done’ secret or app generation concept, this is unique to the gmail address and will need to be done for each and every email address that you wish to send emails from. Next, this sample uses the C# Open Source MailKit library. You can find more details about this here: https://github.com/jstedfast/MailKit   Step 1 – Login to your google account and setup your Google App Password through the security center. https://gmail.com then click in the upper right on your avatar and click “Google Account” Click Security. If you already have 2 step verification and app passwords enabled, click on App Passwords to generate a new one. If you do not, then you will need to enable these to complete this walkthrough / guide. Google profile details On the step below if you do not have 2 factor authentication enabled and verified with your phone, you will need to do that, first.   Next you will need to generate the password to use: Now to generate the actual password. Use whichever name you are comfortable with. Take note of the password (put it in your clipboard or notepad of choice). It will look like this: Step 2 – Install Visual Studio (if needed).

Part II – Copying / Programming

Step 1 – Clone the GitHub Repository https://github.com/bledwards1/MailKit_AzureWebApps_Demo Step 2 – Update the variables inside of the code sample downloaded as shown in the screenshots. The only file you should have to modify is the Default.aspx Lines to modify: 30, 31, and 32 (optional), 37. Feel free to edit any of the others if you’d like to modify such as the subject line, etc. They are also commented clearly in the repository above if you forget... Step 3 – Run the code and check for an email sample!]]> Azure App Service Linux - Adding PHP Extensions https://docs.microsoft.com/archive/blogs/azureossds/azure-app-service-linux-adding-php-extensions Tue, 29 Jan 2019 12:14:34 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5885 Install PHP extensions-
  1.  Go to your KUDU console https://<sitename>.scm.azurewebsites.net
  2.  Select SSH.
  3.  In your SSH session, run the command highlighted in yellow.
 root@3628690f5888:/home/site/wwwroot# pear config-show
 Configuration (channel pear.php.net):
 =====================================
 Auto-discover new Channels     auto_discover    <not set>
 Default Channel                default_channel  pear.php.net
 HTTP Proxy Server Address      http_proxy       <not set>
 PEAR server [DEPRECATED]       master_server    pear.php.net
 Default Channel Mirror         preferred_mirror pear.php.net
 Remote Configuration File      remote_config    <not set>
 PEAR executables directory     bin_dir          /usr/local/bin
 PEAR documentation directory   doc_dir          /usr/local/lib/php/doc
 PHP extension directory        ext_dir          /usr/local/lib/php/extensions/no-debug-non-zts-20151012
 PEAR directory                 php_dir          /usr/local/lib/php
 PEAR Installer cache directory cache_dir        /tmp/pear/cache
 PEAR configuration file        cfg_dir          /usr/local/lib/php/cfg

4.  In the output above, the path for ext_dir is where your extension will be downloaded.  Note the path for later use.

5.  To install an extension, perform the following.  I'll be installing the PHP extension "redis" in this example.

 root@3628690f5888:/home/site/wwwroot# pecl install redis
 downloading redis-4.1.1.tgz ...
 Starting to download redis-4.1.1.tgz (220,894 bytes)
 ..............................................done: 220,894 bytes
 25 source files, building
 running: phpize
 Configuring for:
 PHP Api Version:         20151012
 Zend Module Api No:      20151012
 Zend Extension Api No:   320151012
 enable igbinary serializer support? [no] :
 enable lzf compression support? [no] :
 ……
 Build process completed successfully
 Installing '/usr/local/lib/php/extensions/no-debug-non-zts-20151012/redis.so'
 install ok: channel://pecl.php.net/redis-4.1.1
 configuration option "php_ini" is not set to php.ini location
 You should add "extension=redis.so" to php.ini

6. You'll notice the path to the newly installed extension (highlighted in green) is also returned after it's installed and matches the "ext_dir" path returned from the Pear configurations.

7.  Now that the extension is installed, we'll need to create an "ext" directory under "/home/site" and copy the extension to that directory so that the extension persists if the container is restarted.  Below are the commands to do this.

 root@9a793907fbb0:/home/site/wwwroot# mkdir /home/site/ext
 root@9a793907fbb0:/home/site/wwwroot# cp /home/site/ext /usr/local/lib/php/extensions/no-debug-non-zts-20151012/redis.so /home/site/ext

 Note:  The text may continue and look *garbled.  Don't worry, keep entering the command.

8.  The command highlighted in yellow creates the "ext" directory and the one in green copies the files from the installation location to the new directory.

9.  Once this is done, perform the steps provided at App Service Linux - Update PHP Settings.

Recompiling PHP extensions -

If you need to reconfigure an extension such as GD, please use the following steps.
  1. SSH into your container and run the following
  2. "docker-php-ext-configure gd --with-freetype-dir=/usr --with-jpeg-dir=/usr"
  3. "docker-php-ext-install gd"
  4. cp /usr/local/lib/php/extensions/no-debug-non-zts-20151012/gd.so /home/site/ext
To test, run "service apache2 reload" then go your PHP info page to see if the "freetype" is listed under GD.  If so, update the "extensions.ini" as shown in the "Adding the Extension" section.  We will need to make some further modifications to avoid a conflict with the GD extension if the site were to be rebooted.  In your Application Settings, add the following so that the "extensions.ini" is loaded before the ones under "/usr/local/etc/php/conf.d" Additionally, you can perform the additional steps to move the other INI files to the "/home/site/ini" directory.  In step 3, we'll rename the INI for GD so that it doesn't load the original GD extension on startup but continues to load other extensions.
  1. cp /usr/local/etc/php/conf.d/* /home/site/ini
  2. cd /home/site/ini
  3. mv docker-php-ext-gd.ini docker-php-ext-gd.old

Adding the Extension-

Once the steps performed at App Service Linux - Updating PHP settings are complete, you'll have an "extensions.ini" in your "/home/site/ini" directory.  Below are some options for modifying the extensions.ini file to include our new PHP extension.
Option #1 - Echo
  1. Change directories to /home/site/ini.
  2. Type the following.
 echo "extensions=/home/site/ext/redis.so" >> extensions.ini
Option #2 - Vi
  1. Change directories to /home/site/ini.
  2. Perform the following

 a) vi extensions.ini b) Press "i" on your keyboard to start editing and add the following.

 extension=/home/site/ext/redis.so

c) Press "Esc", then ":wq!" and enter to save.

Once you're done, restart the site using the Azure Portal and you'll now see the extension installed in your PHPInfo page.]]> Azure App Service Linux - Update PHP Settings https://docs.microsoft.com/archive/blogs/azureossds/azure-app-service-linux-update-php-settings Tue, 29 Jan 2019 11:50:06 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5875 Updating PHP Settings-   Settings such as upload_max_filesize, expose_php, and others can be modified using a custom "ini" file. You can use either SSH or Bash to accomplish this.  
  1. Go to your KUDU site https://<sitename>.scm.azurewebsites.net.
  2. Select Bash or SSH from the top menu.
  3. In Bash/SSH, go to your "/home/site" directory.
  4. Create a directory called "ini" (i.e. mkdir ini)
  5. Change directories to "ini".
  6. We'll need to create an "ini" file to add our settings to. In this example, I'm using "extensions.ini". There are no file editors such as Vi, Vim, or Nano so we'll simply use echo to add the settings to the file. I'm changing the "upload_max_filesize" from 2M to 50M. Below is the command that I used to add the setting and create an "extensions.ini" file if one doesn't already exist.
  NOTE: If you already have an extensions.ini file, you can use the same command which will add the new setting to the file. 
/home/site/ini>echo "upload_max_filesize=50M" >> extensions.ini

/home/site/ini>cat extensions.ini

upload_max_filesize=50M

/home/site/ini>
If using SSH, you can use vi to create/edit the extensions file using the following commands. a) vi extensions.ini b) Press "i" on your keyboard to start editing and add the following. 
upload_max_filesize=50M
c) Press "Esc", then ":wq!" and enter to save.   Add an Application Setting-   We'll now need to go to the Azure Portal and add an Application Setting to scan the "ini" directory that we just created to apply the change for upload_max_filesize.  
  1. Go to the Azure Portal (https://portal.azure.com) and select your App Service Linux PHP application.
  2. Select Application Settings for the app.
  3. Under the Application settings section, press the "+ Add new setting".
  4. For the App Setting Name, enter "PHP_INI_SCAN_DIR".
  5. For the value, enter "/usr/local/etc/php/conf.d:/home/site/ini"
  NOTE: If you're you've recompiled a PHP extension such as GD, perform the steps at "Recompiling PHP Extensions" at Azure App Service - Adding PHP Extensions and enter a value of "/home/site/ini" and omit the "/usr/local/etc/php/conf.d:" portion.  
  1. The first portion of the value is the location of other ini files that come with the Docker container and the second part (after the ":") is the directory that contains our new ini file.
  2. Press the save button.
  Testing-

1. You should now see the upload_max_filesize increase from 2M to 50M if you have a PHP info page. If not, create one by going to your /home/site/wwwroot directory and perform the following.

echo "<?php phpinfo();" >> info.php

2. You should now see the values by going to https://<sitename>.azurewebsites.net/info.php

     ]]> Building Python Functions App that use Native Modules – Custom Docker https://docs.microsoft.com/archive/blogs/azureossds/building-python-functions-app-that-use-native-modules-custom-docker Wed, 31 Oct 2018 14:23:43 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5805 Prerequisites To build and test locally, you will need to: To install Azure Functions Core tools you will need also these requirements:
  1. Install .NET Core 2.1 for Windows.
  2. Install Node.js, which includes npm. For version 2.x of the tools, only Node.js 8.5 and later versions are supported.
  3. Install the Core Tools package: npm install -g azure-functions-core-tools

Create and activate a virtual environment

To create a Functions project, it is required that you work in a Python 3.6 virtual environment. Run the following commands to create and activate a virtual environment named env. # In Bash python3.6 -m venv env source env/bin/activate # In PowerShell py -3.6 -m venv env env\scripts\activate # In CMD python -m venv env env\scripts\activate

Create a local Functions Project

To create a Functions project, it is required that you work in a Python 3.6 virtual environment. Run the following commands to create and activate a virtual environment named env. In the terminal window or from a command prompt, run the following command:

func init MyFunctionProj --worker-runtime python –docker func init . --worker-runtime python --docker

You will see something like the following output.

Installing wheel package Installing azure-functions==1.0.0a5 package Installing azure-functions-worker==1.0.0a6 package Running pip freeze Writing .funcignore Writing .gitignore Writing host.json Writing local.settings.json Writing D:\__Documents\WebAppProjects\functions-python-3\.vscode\extensions.json Writing Dockerfile

This generates a Dockerfile with the following content:

FROM mcr.microsoft.com/azure-functions/python:2.0

COPY . /home/site/wwwroot

RUN cd /home/site/wwwroot && \

    pip install -r requirements.txt

Create a function

https://github.com/Azure/azure-functions-python-worker/wiki/Create-your-first-Python-function#create-a-function

Run the function locally

https://github.com/Azure/azure-functions-python-worker/wiki/Create-your-first-Python-function#run-the-function-locally

Run locally as Docker container

Using Docker, run the following command. Replace <imagename> and <tag> with preferred names.

docker build . --tag <imagename>:<tag> (example) docker build . -- pythonfunction:v1

Once image has been build you could run the following command to start the image:

docker run -p <portexposed>:<portusedinside> <imagename>:<tag> (example) docker run -p 8080:80 pythonfunction:v1

Once started, you could browse to https://localhost:8080 (using example) to view your function running.

Deploy your function app

You could use Docker Hub or Azure Container Registry to deploy your Docker image.

Push image to Docker Hub

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal#push-image-to-acr

First Create a container registry

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal#create-a-container-registry

Log in to ACR

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal#create-a-container-registry

Push image to ACR

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal#push-image-to-acr

Create function app via Azure Portal

Select the New button found on the upper left-hand corner of the Azure portal, then select Compute > Function App. When configuring the settings, select Linux (Preview) for OS and Docker Image for Publish. Under Configure Container, select either Azure container Registry or Docker Hub depending on how you deployed your Docker image. Once deployed, you will be able to access the Function Apps page Once deployed, you can test your Function App: Be sure to change <functionappname> and <function-name> with your functions values. https://<functionappname>.azurewebsites.com/api/<function-name>]]> Restrict access to login for the WordPress running on Azure web app container https://docs.microsoft.com/archive/blogs/azureossds/restrict-access-to-login-for-the-wordpress-running-on-azure-web-app-container Fri, 12 Oct 2018 19:17:52 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5765 2. Add the code below to ".htaccess", replace the IP "xx.xx.xx.xx" by that you allow to access wp-login.php 
<Files wp-login.php>
Order Deny,Allow
Deny from all
SetENVIf X-Client-IP "xx.xx.xx.xx" AllowAccess
Allow from env=AllowAccess
</Files>
Note: Since /wp-admin will direct to wp-login.php, no need to define the rule for wp-admin]]> RewriteRule sample for WordPress in subdirectory https://docs.microsoft.com/archive/blogs/azureossds/web-config-sample-for-wordpress-nested-in-subdirectory Mon, 01 Oct 2018 13:45:27 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5735   if use "Post name" Permalink setting, with default web.config, articles in subdirectory might give 404 (not found), for example,   For this problem, you can modify web.config to exclude subdirectory "blogs" from main site rewrite rules, here is sample web.config, 
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
  <rewrite>
  <rules>
    <rule name="Imported Rule 1" stopProcessing="true">
      <match url="^index.php$" ignoreCase="false" />
      <action type="None" />
    </rule>
    <rule name="Imported Rule 2" stopProcessing="true">
      <match url="." ignoreCase="false" />
      <conditions>
        <!--# Include in the next line all folders to exclude-->
        <add input="{URL}" pattern="(blogs)" negate="true" />
        <add input="{REQUEST_FILENAME}" matchType="IsFile" ignoreCase="false" negate="true" />
        <add input="{REQUEST_FILENAME}" matchType="IsDirectory" ignoreCase="false" negate="true" />
      </conditions>
      <action type="Rewrite" url="/index.php" />
    </rule>
  </rules>
  </rewrite>
</system.webServer>
</configuration>
  If the WordPress sites are hosted on Apache on Azure web app for containers, modify wwwroot/.htaccess, for example, 
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
# Include in the next line all folders to exclude RewriteCond %{REQUEST_URI} !(blogs) [NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress]]> How to change memory_limit on Wordpress Web App for Linux on Azure https://docs.microsoft.com/archive/blogs/azureossds/how-to-change-memory_limit-on-wordpress-web-app-for-linux-on-azure Thu, 27 Sep 2018 12:41:37 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5645 here). Step 1: Login to the portal and go to the "Advanced Tools" section and go to the SSH option. Step 2: Copy these entries and place them in the .htaccess file located at /home/site/wwwroot/ using your preferred method. I prefer to use vi. php_value memory_limit 256M php_value post_max_size 256M php_value upload_max_filesize 128M Step 3: Save the file using vi to add these entries into the .htaccess file. It should look something like this once you are done: Step 4: Confirm they have been set by creating a phpinfo.php file and make sure the settings are correct. Or, you can check in the Wordpress Media Upload tool: You can see that these settings have now been updated and no need to make a custom Docker image just to edit a few PHP variables.   Let me know what other interesting settings work in our .htaccess files in the comments below!]]> How to set node version for Windows node.js webapp from Azure Portal https://docs.microsoft.com/archive/blogs/azureossds/how-to-set-node-version-for-windows-node-js-webapp-from-azure-portal Tue, 25 Sep 2018 16:35:42 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5675 Create the Azure WebApp
  • Create new WebApp using Azure portal
 
  • Set the App name, Resource Group and click "Create"
 
  • Wait for deployment to succeed and then click on Application Settings for the new Webapp.
  • Add a new setting with App Setting Name "WEBSITE_NODE_DEFAULT_VERSION" and Value "8.9.4" and click Save. If you would like to use a different version of node, please refer to the section "How to find available node.js versions for Windows Webapps" below.
  • You can now start developing your node.js application in Azure Environment.

How to find available node.js versions for Windows Webapps.

For nodejs release schedule, please refer to https://github.com/nodejs/Release To find current nodejs versions available in Azure Windows WebApps, navigate to this link: https://<yourwebappname>.scm.azurewebsites.net/api/diagnostics/runtime You can only use the versions available in this list. New versions are added regularly, so please check for newer versions using the /api/diagnostics/runtime url above.

Common Error that indicates the node.js version is missing or incorrect.

If your application is getting the following error, please check whether WEBSITE_NODE_DEFAULT_VERSION is set to a valid value. 
Application has thrown an uncaught exception and is terminated:
SyntaxError: Unexpected token {
at Module._compile (module.js:434:25)
at Object..js (module.js:464:10)
at Module.load (module.js:353:31)
at Function._load (module.js:311:12)
at Module.require (module.js:359:17)
at require (module.js:375:17)
at Object.<anonymous> (D:\Program Files (x86)\iisnode\interceptor.js:459:1)
at Module._compile (module.js:446:26)
at Object..js (module.js:464:10)
at Module.load (module.js:353:31)
]]> Configuring node.js application on Azure App Service with Azure Blob Storage https://docs.microsoft.com/archive/blogs/azureossds/configuring-node-js-application-on-azure-app-service-with-azure-blob-storage Thu, 30 Aug 2018 05:39:51 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5625

In this article, we will learn about configuring the node js applications deployed on Azure App Services with the Azure blob storage.

If you would like to store the application logs in a blob storage on azure for the node.js applications, you would need to follow the steps below. It basically includes 2 main steps:

  1. Enabling from Portal
  2. Configuring from the code

Enabling from Portal

· Navigate to your webapp from the azure portal

· Choose the Diagnostic Logs blade. For application level logging, choose Blob storage as shown below. If you would like to choose file system, please check out the blog post here

clip_image002

Configuring from the code

  • In your application, install the packages winston & winston-azure-blob-transport by the running the commands below

npm install winston

npm install winston-azure-blob-transport

  • Now, use the code below in order to configure them from the application

var winston = require("winston");

require("winston-azure-blob-transport");

var logger = new (winston.Logger)({

    transports: [

      new (winston.transports.AzureBlob)({

        account: {

          name: process.env.ACCOUNT_NAME,

          key: process.env.ACCOUNT_KEY

        },

        containerName: process.env.CONTAINER_NAME,

        blobName: "test.log",

        level: "info"

      })

    ]

  });

logger.info("Hello!");


  • test.log in the above code snippet is the name of the blob where the logs get stored.
  • You would be able to get the Account name, Account key and the container name from the Azure storage account view
  • You would need to make use of Storage Explorer in order to check the log file as shown below.

clip_image004]]> Debugging Node.js applications on Azure App Services Linux/containers https://docs.microsoft.com/archive/blogs/azureossds/debugging-node-js-applications-on-azure-app-services-linux-containers Thu, 30 Aug 2018 03:50:42 GMT https://blogs.msdn.microsoft.com/azureossds/?p=5405 App Service Windows.  In this blog, you will learn how to debug the node.js applications that are hosted on Azure App Service Linux / Azure webapp for containers. Enabling logs on linux offerings of AppService is fairly easier and pretty straight forward when compared to Windows. Enable Logging on Linux

  • Navigate to your webapp from the azure portal
  • Choose the Diagnostic Logs blade. Here we have only one option to enable logs which is docker container logs unlike in Windows, where we have the storage option as well. As of today, we do not have the option of storing the logs to blob storage in App Service Linux.
  • Choose File System, specify the retention period of your choice. This will delete the logs that are older than specified number of days
clip_image001
  • This will gather all the STDOUT and STDERR logs of the container into /home/LogFiles folder
  • Once you have configured using above step, you will be able to access these log files by following the steps below
  1.   Go to your file system by browsing https://{webapp_name}.scm.azurewebsites.net url (called as kudu site)
  2.   Click on Debug Console –> Bash. If it is app service Linux, you can alternatively choose SSH option
  3.   Please note that SSH works only for App Service Linux. But for Webapp Containers, you would need to configure it by following the official documentation here
  4.   Navigate to the LogFiles folder by running the command “cd LogFiles”
  5.   Now run the command “ls -lrt” to list all the log files with the latest one in the bottom. The stderr and stdout logs are stored in the file that ends with default_docker.log as shown below
clip_image002
  • You can view this by running the command cat <filename>. If your application has any stdout/stderr configured, it will be seen in this log file.
clip_image003
  • You can also download it using FTP and steps to follow are specified here
  • If you are only looking for the latest docker logs, the quickest way is to go to Kudu console and click on Current Docker Logs option as shown below. However, this will only give the information related to the container, but not the stdout/stderr logs.
clip_image004
  • Once you click on this link, you will be redirected to a new page with all the details related to the latest docker logs
clip_image005
  • Now, copy paste the link that is highlighted into the new tab and you should see the output as below
clip_image006]]>