You can clone with
HTTPS or Subversion.
All vars should have an iisnode- prefix, for example IISNODE-ENABLEDEBUGGING. This will make it easy to configure iisnode from the Azure portal.
Here is the order of precedence for how config values will be read
With this change iisnode allows specification of all of its settings using environment variables.
Environment variables must be set in the environment block of the IIS worker process (w3wp.exe) to be effective. Naming of the environment variables follows a pattern of IISNODE_<SettingName>, where <SettingName> corresponds to any of the configuration settings specified in iisnode.yml. String configuration settings are used literally. Integer configuration settings allow values between 0 and LONG_MAX. Boolean configuration settings should be specified as 1 or 0.
This is the order of precedence of configuration settings (with 1 taking precedence over 2, etc.):
fix #220: support for environment variable based configuration