Environment Setup for Node.js web apps for Azure App Service

The instructions in this tutorial can be followed on any operating system that can run Node.js.

Below is the list of installation required

  • Node.js – Click here to install setup
    • Node.js® is a JavaScript runtime built on Chrome’s V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient.

  • Bower – Click here to install setup
    • Bower can manage components that contain HTML, CSS, JavaScript, fonts or even image files. Bower doesn’t concatenate or minify code or do anything else – it just installs the right versions of the packages you need and their dependencies.

  • Yeoman – Click here to install setup
    • Yeoman helps you to kickstart new projects, prescribing best practices and tools to help you stay productive.

      To do so, Yeoman provides a generator ecosystem. A generator is basically a plugin that can be run with the `yo` command to scaffold complete projects or useful parts.

  • Git – Click here to install setup
    • The Git is a Source Code Management (SCM).The Git feature that really makes it stand apart from nearly every other SCM out there is its branching model.

      Git allows and encourages you to have multiple local branches that can be entirely independent of each other. The creation, merging, and deletion of those lines of development takes seconds.

  • Azure CLI 2.0 Preview – Click here to install setup
    • Microsoft has improved and update Azure CLI to provide a great native command-line experience for managing Azure resources.
  • A Microsoft Azure account. If you don’t have an account, you can sign up for a free trial or activate your Visual Studio subscriber benefits.
  • Also we need to install
    • Install Azure SDK for Node.js: Use and manage your Azure resources with Node.js

      Get the SDK from npm:
      Use below command
      npm install azure

      <a href=”https://www.olark.com/site/8335-828-10-8454/contact” title=”Contact us” target=”_blank”>Questions? Feedback?</a> powered by <a href=”http://www.olark.com?welcome” title=”Olark live chat software”>Olark live chat software</a>


Powershell and CSOM: Remote machine environment setup requirement

In order to enable SharePoint Online PowerShell Script execution from your remote machine, below are the steps required to follow on remote machine,

Step 1

SharePoint Server 2013 Client Components SDK – Download and Install at your Remote machine, Download SharePoint Server Client SDK .
This is required to enable usage of CSOM to your PowerShell script for O365 tenant.
Download as per available remote machine environment,

Install after download,

Step 2

Install Windows PowerShell 3.0 from Windows Management Framework 3.0 .

Step 3

Install the SharePoint Online Management Shell from the Microsoft Download Center .

Step 4

Set the policies, if not already set,

Check policies by using Windows PowerShell script command,

Get-ExecutionPolicy -List

The result will look similar to the following sample output:

Scope    ExecutionPolicy
—–    —————
MachinePolicy          Undefined
UserPolicy          Undefined
Process          Undefined
CurrentUser       RemoteSigned
LocalMachine          AllSigned

If not as above, use below command,

Set-ExecutionPolicy -ExecutionPolicy <PolicyName>

e.g to set CurrentUser policy,

Set-ExecutionPolicy -ExecutionPolicy  CurrentUser

When it ask for value use below,
Click here for detailed information on RemoteSigned
Hope you find this article useful.