Setup python development server

[fungjj92]

Overview

As we migrate the app to a static site, we'll need our own dev environment apart from the current Visual Studio .NET setup from which we can work and model static site architecture. As per the ADR, we will use a python environment and thusly for the dev server use python's SimpleHTTPServer. Keeping to wider Azavea convention, we will use the STRTA workflow.

Connects #1085

Demo

Notes

There's one more 403 accessing use.js -- the file path is incorrect, as I tried to solve for other similar failures in e56043e, but I wasn't able to figure out where use.js was even being called and loaded. It doesn't seem like a big deal and will likely be fixed as we migrate and update the rest of the app and assets, which will additionally address the rest of the expected console errors.

Testing Instructions

Either:

• Clone this repo locally, not in your windows VM, and checkout the branch or
• Pull down this branch in the Windows VM: do not run the project in Visual Studio

Then:

• ./scripts/server
• open a working index page (with a lot of broken templated code, intentionally) at http://localhost:54633

[caseycesari]

Use.js is located here:

src/GeositeFramework/js/lib/use.js

[fungjj92]

Indeed! I found the file, but couldn't figure out where it was being called. If anything, https://github.com/CoastalResilienceNetwork/GeositeFramework/blob/23742882ecd8bdddb017ceb38cbdc768e30d4805/src/GeositeFramework/index.html#L841 but removing this line didn't make a difference.

[caseycesari]

Oh sorry. Misread the comment. Yeah, I think use.js loading depends on some back-end processing. Want to capture that in an issue so we don't forget?

[fungjj92]

Updated ./scripts/server to use Python. Ready for another look 👍

[fungjj92]

Note, there are a few new console errors for improper pathnames for font files. Added issue #1108

[fungjj92]

Logging added. Merging