$Env:PSModulePaththat enables the user to load modules from. For example, you could have all your modules stored in
C:\PowerShellModules\and then you would add that path to the
$Env:PSModulePathenvironment variable. If you configure it in this manner, you'll be able to upgrade Universal Dashboard in a single place and all your websites will load the new module.
web.configfile included with UD as well as your script to the websites folder. You can click Explore to view this folder.
web.configfile should start PowerShell.exe or Pwsh.exe. As an argument to the process, you'll want to include the dashboard script. Edit the
aspNetCorenode in the
web.configfile to include this information.
.ps1file and place it in the
wwwrootfolder. The dashboard should contain a dashboard definition and a call to
web.configfile and a PowerShell script that will execute when accessing the website.
index.htmlfile in the
hrefattribute to match the relative URL of your UD installation. If you wanted to have the URL resolve to
http://myServer:8080/dashboards/dashboardyou would set the value of the
index.htmllooks like this.
netstandard2.0folder within the module installation directory. This will ensure that the license is persistent throughout restarts.
web.configfile. You can change the
stdoutLogFilepath to a location that IIS has the permissions to write to. You can then add
Enable-UDLoggingto the top of your
dashboard.ps1file to turn on console logging for Universal Dashboard. This is a complete