Doc for Jetty webapp configuration

[janezomgzomg]

• Added a doc to /docs/ to explain basic configuration of a View webapp in Jetty

[erikhatcher]

I'd like to see these instructions specifically for deploying View into a running instance of Fusion... and thus the instructions would be to copy it under apps/jetty/ui/webapps/<view name> kinda thing. I'd rather not encourage users to deploy into a differently downloaded independent version of Jetty, and we've got a handy running instance in Fusion as it is. Win win!

[JoshEllinger]

@erikhatcher any suggestions as to how an average view user might add redirect rules to jetty inside fusion?

With that knowledge I think it would be possible and a good idea to be more specific to fusion here.

[erikhatcher]

@JoshEllinger What kind of redirect rule is needed? I'm confused - the document being added here to put View into a Jetty doesn't mentioned anything about redirects.

[JoshEllinger]

@erikhatcher view is a single page app, which means angular js is handling the routing. In order to work 100% inside any web server redirect rules are needed, such that urls such as http://thisurl.com/folder/something are redirected to http://thisurl.com/folder/index.html which then routes via js correctly to the new url path of /folder/something. (Folder is optional and not needed for view)

Without this redirect links from copy paste or refresh would not work as the index.html file would never get that information and instead jetty would think the url is pointing at nonexistent empty folders

[erikhatcher]

Does this show it doing what you want?

$ pwd
/Users/erikhatcher/fusion-2.3/apps/jetty/ui/webapps/path_test
$ cat index.html 
Hi!
$ curl -L http://localhost:8764/path_test
Hi!

[JoshEllinger]

@janezomgzomg as we discussed, to finish this out first we need to determine if view will work on fusion's jetty. at that point we can update the instructions here. This will be important to know for how the field tells customers to install view 😄 .

[janezomgzomg]

@JoshEllinger heh, noted 👌

[JoshEllinger]

Marking as wontfix for now, theres extra complexity here we are not going to tackle right now. Lets re-open if we decide to come back to this.