WAS currently responds with Hello World JSON at /.
When the WAS web ui is served via FastAPI/WAS we should respond with something more meaningful for users accessing WAS with a browser.
We should serve up simple nginx/apache style default HTML that at least lets the user know they have correctly accessed their WAS installation. For flexibility and future use it should include links to docs at heywillow.io, links to the admin interface, and potentially a reference to the FastAPI autogenerated documentation for the WAS API.
WAS currently responds with Hello World JSON at /.
When the WAS web ui is served via FastAPI/WAS we should respond with something more meaningful for users accessing WAS with a browser.
We should serve up simple nginx/apache style default HTML that at least lets the user know they have correctly accessed their WAS installation. For flexibility and future use it should include links to docs at heywillow.io, links to the admin interface, and potentially a reference to the FastAPI autogenerated documentation for the WAS API.