The web assets (like HTML and indi.js) had a leading /, this meant if this app was behind a reverse proxy with a context that the app wouldn't work
In HTML an asset with a leading / in its URI is shortcut for the whole scheme, host, port and then the path to asset, by removing the leading / it means that asset is loaded relative to the current asset
The API within the indi.js also needed to use a relative path
I have tested this behind an Nginx server as well as being a standalone app accessing it directly.
I have tested this behind an Nginx server as well as being a standalone app accessing it directly.