v3
User Interfaces
Configuration
Single-File
Single-file hosting and configuration for PowerShell Universal.
Single-file hosting is deprecated and will be removed in the next major version.
Single File Hosting and Configuration
You can configure and run the PowerShell Universal server from the command line. The
Start-PSUServer and Install-PSUServer cmdlets can be used to install, configure and run a Universal instance in a single file.Installing
To install from the command line, use
Install-PSUServer. By default, it will store the latest version of the PowerShell Universal Server to the $Env:ProgramData\PowerShellUniversal folder. You can specify an alternate path and optionally add the older to the $Env:Path environment variable .1
Install-PSUServer -AddToPath
Copied!
Once the server is installed, you can start it with
Start-PSUServer.Configuration
You can configure PowerShell Universal from the command line using
Start-PSUServer and the -Configuration parameter. You can use the same cmdlets that you would use in the various configuration files but utilize a single file. You should save this file and then execute the PS1 file. Any changes to the file will be auto-reloaded.1
Start-PSUServer -Port 8080 -Configuration {
2
New-PSUEndpoint -Method GET -Url '/user' -Endpoint { "User1" }
3
New-PSUEndpoint -Method POST -Url '/user' -Endpoint { $Body }
4
New-PSUPublishedFolder -Path C:\images -RequestPath /images
5
New-PSUDashboard -Name 'Dashboard' -BaseUrl '/' -Framework "UniversalDashboard:Latest" -Content {
6
New-UDDashboard -Title 'Test' -Content {
7
New-UDTypography -Text 'Hello, world!'
8
}
9
}
10
} -ExecutablePath "$Env:ProgramData\PowerShellUniversal\Universal.Server.exe"
Copied!
Limitations
Single file hosting has some limitations in terms of scoping. Variables, functions and modules used within the parent scope or the configuration script block scope will not be accessible in the dashboard, endpoint or script content scopes.
1
$MyVariable = "Nice"
2
​
3
Start-PSUServer -Port 8080 -Configuration {
4
# $MyVariable available here
5
New-PSUEndpoint -Method GET -Url '/user' -Endpoint {
6
# $MyVariable not available here
7
}
8
New-PSUDashboard -Name 'Dashboard' -BaseUrl '/' -Framework "UniversalDashboard:Latest" -Content {
9
# $MyVariable not available here
10
New-UDDashboard -Title 'Test' -Content {
11
New-UDTypography -Text 'Hello, world!'
12
}
13
}
14
}
Copied!
You can work around these limitations by using variables and environments.
1
$MyVariable = "Nice"
2
​
3
Start-PSUServer -Port 8080 -Configuration {
4
New-PSUVariable -Name 'MyVariable' -Value $MyVariable
5
# $MyVariable available here
6
New-PSUEndpoint -Method GET -Url '/user' -Endpoint {
7
# $MyVariable available here
8
}
9
New-PSUDashboard -Name 'Dashboard' -BaseUrl '/' -Framework "UniversalDashboard:Latest" -Content {
10
# $MyVariable available here
11
New-UDDashboard -Title 'Test' -Content {
12
New-UDTypography -Text 'Hello, world!'
13
}
14
}
15
}
Copied!
Referencing Other Files
The single-file hosting and configuration does not actually require the use of a single file. Rather, it means that you have a single entry point for the hosting and configuration of your PowerShell Universal server. You can reference other files within the
-Configuration script block parameter.For example, if you wanted to load endpoints from a nested folder, you could do the following.
1
Start-PSUServer -Port 8080 -Configuration {
2
Get-ChildItem (Join-Path $PSScriptRoot 'endpoints') | ForEach-Object {
3
& $_.FullPath
4
}
5
}
Copied!
With this configuration, you can have an
endpoints folder within the same directory as your root file and they will be loaded automatically when the server starts of the files change.Last modified 3mo ago