localtileserver icon indicating copy to clipboard operation
localtileserver copied to clipboard

Add a utility to the Report that will help decipher if a user is in a "remote" environment

Open banesullivan opened this issue 3 years ago • 1 comments

Users are regularly running into issues setting up/using localtileserver in remote environments -- whether by running Jupyter on a remote server or within an isolated network on their own device (e.g., within Docker).

I'm thinking that there might be a way to provide a surface-level test as to whether the user is in one of these scenarios. It would be nice to provide a utility method that would try to do this deciphering and then include that as additional metadata for this package's scooby report. That way, when a user has an issue, they can include a scooby report that would include something like:

remote status : likely JupyterHub

with maybe a few possible scenarios:

  • likely JupyterHub
  • Isolated network
  • Unknown
  • Running locally

banesullivan avatar Mar 30 '22 16:03 banesullivan

At the very least, I could provide a test widget that would give the user errors rather than silently failing like the map views currently do (because a 404 tile URL is actually okay - means that there's no data for that tile in many cases)

banesullivan avatar Mar 30 '22 16:03 banesullivan

Too difficult to implement

banesullivan avatar Jan 21 '24 22:01 banesullivan