Published folders allow you to share a local folder through your Universal website. Any file within the published folder will be accessible via a web request. This can be helpful for storing images or other files that you may want to provide via your Universal Dashboard.
Dashboard / Published Folders page, you can click Add Published Folder. You will need to enter the local path as well as the request path. The local path is the folder that you wish to publish. The request path is the path that the end user will request to download the files from the folder.
You can choose to turn on authentication and authorization for the folder.
Once the folder has been published, it will be listed in the published folders table.
You can now download files that are found in the published folder by visit the request path. In the example above, I could visit the following URL to download the test.txt file.
You'll notice that unauthenticated requests will not be able to access the file.
PS C:\src\universal\src> invoke-webrequest http://localhost:5000/src/test.txtInvoke-WebRequest: Response status code does not indicate success: 401 (Unauthorized).
Default documents allow you to load files when a user specifies the folder and not the document within a folder. This can be handy when a user visits
/docs but does not specify
/docs/index.html. Instead of returning a 404, you can return the
index.html when the user specifies
To configure default documents, set the
-DefaultDocument parameter on
New-PSUPublishedFolder -Path C:\website -RequestPath /docs -DefaultDocument @("index.hml")
Create a published folder. Can be used in the
publishedFolders.ps1 file or via the management REST API.
The relative path to server documents from.
The absolute file system path to server files from.
Whether authentication is required to access this folder.
Roles that can access this folder. Leave blank for any role.
Default documents to server with out specifying the file name.
The URL to the PSU management API.
The AppToken used to access the PSU management API
Whether to use the current user's credentials to access the PSU management API