But as of today they don’t quite match what I’m seeing in the wild. To get it to work for me, when I modified the Index.html file in the Client folder, href needs to be changed from “/” to the relative path from the site root to the subfolder of your app. E.g. - “/MyDBTest/” or “/Apps/DB1/”
Unlike the docs, I needed to add a trailing slash.
In addition, in the same Index.html file, I had to add that relative folder path to the beginning of the paths for the javascript files, “/MyDBTest/main.[guid].bundle.js” and “/MyDBTest/vendor.[guid].bundle.js”.
I copied the universaldashboard.community folder contents into my key folder.
I edited the \inetpub\fbsession\key\client\index.html as you suggested above.
Yes, it needs to be an application. (I assume. Mine is, and I can’t imagine it working otherwise.)
Delete “/fbsession” from the paths in Index.html. What you are putting in there is the relative path from the root of fbsession to the application or file.
Yeah, the font errors always show up. Not sure what’s up with that.
By “getting my Title”, do you mean a UDTitle that’s defined on the page, or the NavBar at the top of the page?
If the former, there’s something wrong with your page.
If the latter, that means UD is working well enough to serve up pages if it can figure out which page to serve and how to serve it, but in this case it couldn’t. (Or there’s something wrong with your page.)
Open Developer Tools in Chrome, go to the Network tab, then reload your UD page. It will tell you what it’s trying to load and what’s successful or not, which should point you to the right direction.
Couple more possible gotcha’s. I worked around these when they were problems, and as my workarounds are still place, I don’t know if they are still problems.
When looking for a page to serve, UD grabs the first partial match, rather than the fullest match. The work around is to sort the pages like so before feeding them to New-UDDashboard. We’re looking at both Name and URL, because static pages have the one, and dynamic pages have the other. We trim leading slashes because only dynamic pages have those.
Defining a default home page was not working for me in this context. So for a home page, instead of defining a static page with the -Name “Home” with -DefaultHomePage set, I defined a dynamic page with the -URL ‘/’, and changed the -Content to an -Endpoint. (This dropped the home page from the default navigation list, but I’m willing to live with that. I put a link to the home page in a “footer” on each page. (To faciliate that, I put the home page link–the relative path to your dashboard, ‘/key’ in your case-- in a $Cache variable in the Dashboard script, for use by each page, as needed.))
Create a dashboard.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.
You shouldn’t be running your script in VS Code once it’s deployed to IIS. IIS will be starting the dashboard. The reason you are getting permission denied in VS Code is because something else is listening on the port that you have assign.
If you open a browser and go to the address: http://localhost:80, what happens? If you’ve configured IIS as stated in the article, it should show the dashboard.
Delete Module from C:\Windows\system32\WindowsPowerShell\v1.0\Modules\UniversalDashBoard
Delete all files related UD in wwwroot directory
Reboot the computer
Install UD and it installs on C:\Program Files\WindowsPowerShell\Modules
copied files from C:\Program Files\WindowsPowerShell\Modules\UniversalDashboard\2.3.2 to wwwroot
Now I am able to use iis to launch the website. I did not copy UniversalDashboard module to C:\Windows\System32\WindowsPowerShell\v1.0\Modules