Offline use with custom endpoints

Target Use Case

I am using deck.gl in a completely isolated environment with my own tile servers, style.json, theme.css, and javascript files. I am somewhat new to this kind of development so forgive me if I missed something in the current issues or am asking a silly question, but I think it would be valuable to have a field in the to_html() function that can point to different endpoints. The examples I found on this page, #4290 and #4405 are close to what I'm looking for but not quite. A user commented on the bottom of the discussion with an example of what I'm experiencing: https://github.com/visgl/deck.gl/issues/4290#issuecomment-1685241874

A quick example of some things I have tried:

• porting files on the internet to the isolated server to then copy and paste into the resultant html file (but this doesn't work because each of these files points to other locations like mapbox.com that don't exist on my isolated server)
• creating my own style files and pointing to those (not confident why this doesn't work, but my guess is it doesn't cover all the bases

Proposal

Essentially I'm looking for an additional feature or even documentation denoting necessary steps for redirecting these endpoints. Even some documentation describing what features are required by each of the current endpoints would be helpful as well.

Start at the to_html() entry point and review issues #4290 and #4405, including the linked comment, to understand the existing endpoint assumptions. Define what endpoint configuration or documentation is needed for isolated tile servers, style.json, theme.css, and JavaScript files, and consider the required behavior for a generated HTML file to work without internet access.