Stuck on loading Screen, GET /public_html/app HTTP/1.1 404

[jdvala]

I am trying to use termite-ui for topic modeling, however, I am unable to make it work.
OS: Debian 9
RAM: 8GB

I followed the instructions in the README.md

The logs are below

The group-in-a-box visualization is now available at http://127.0.0.1:8000/
Serving HTTP on 0.0.0.0 port 8000 ...

127.0.0.1 - - [30/Oct/2018 12:06:11] code 404, message File not found

127.0.0.1 - - [30/Oct/2018 12:06:11] "GET /public_html/app HTTP/1.1" 404 -

127.0.0.1 - - [30/Oct/2018 12:06:12] code 404, message File not found

127.0.0.1 - - [30/Oct/2018 12:06:12] "GET /favicon.ico HTTP/1.1" 404 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET / HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /libs/fluxweed/style.css HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /css/style.css HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /bower_components/angular/angular.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /bower_components/angular-route/angular-route.js 
HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /bower_components/d3/d3.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /bower_components/underscore/underscore.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /bower_components/jquery/dist/jquery.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /js/app.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /js/services.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /js/controllers.js HTTP/1.1" 200 -

127.0.0.1 - - [30/Oct/2018 12:06:36] "GET /js/directives.js HTTP/1.1" 200 -

I suspect the instructions to run this UI is incomplete or may be I have not been able to find hem.

[alisonmsmith]

The data server must also be running. Instructions for that are here: https://github.com/uwdata/termite-data-server; however, even after getting the server running I'm still seeing a no-access-control error. It's possible the server will need to be updated to support cross browser requests or we'll need to set up a proxy from the UI to work around the error.