$Env:PSModulePath
that 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:PSModulePath
environment 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.config
file included with UD as well as your script to the websites folder. You can click Explore to view this folder.web.config
file should start PowerShell.exe or Pwsh.exe. As an argument to the process, you'll want to include the dashboard script. Edit the aspNetCore
node in the web.config
file to include this information..ps1
file and place it in the wwwroot
folder. The dashboard should contain a dashboard definition and a call to Start-UDDashboard
with the -Wait
parameter specified.web.config
file and a PowerShell script that will execute when accessing the website.index.html
file in the client
folder.base
's href
attribute to match the relative URL of your UD installation. If you wanted to have the URL resolve to http://myServer:8080/dashboards/dashboard
you would set the value of the href
attribute to /dashboards/dashboard/
./
.index.html
looks like this.net472
or the netstandard2.0
folder within the module installation directory. This will ensure that the license is persistent throughout restarts.web.config
file. You can change the stdoutLogFile
path to a location that IIS has the permissions to write to. You can then add Enable-UDLogging
to the top of your dashboard.ps1
file to turn on console logging for Universal Dashboard. This is a complete web.config
example