Current HTTP setup puts a lot of load on AuthD #47
Description
Right now, to keep the web config simple, I have DGD serving its own HTML web client, its own JS and CSS files, etc. This isn't particularly efficient -- especially because DGD will contact AuthD for every file. It could be fixed with a better NGinX configuration that checked (on a port other than 10080) for static files, served them if present, and fell back to DGD on port 10080 as a back end.
This would also solve the logout problem we currently have with cookies -- by keeping everything on a single port handled by NGinX for static files and DGD for dynamic files, we can keep the cookies unified. Right now that's not happening.