403: Forbidden Error due to Plotly CDN being down - Need to point to alternative JS sources about polyaxon

[bastianerh]

For production deployment this flag should be enabled, we used the CDNs for Polyaxon CE deployments because lot of users try Polyaxon on very small instances first and loading all vendor libraries put a lot of pressure on the server and then they create tickets asking why it does not work.

We are in the process of finalizing Polyaxon v2 and we might just flip the flag to make CDNs opt-in instead of opt-out.

All ui flags are documented here: https://polyaxon.com/docs/setup/platform/common-reference/#ui

[bastianerh]

You can redeploy/upgrade your installation to use local packages instead of cdns with:

...
ui:
  offline: true
...

[arek-widelab]

What about resources like https://cdn.plot.ly/usa_110m.json?
Is it possible to replace that path as well using plotly api?

EDIT:
Yes, it is but it's rather a workaround for CDN down, not production ready solution.

Using plotly.js in config there is a field topojsonURL which can be overwritten by:
topojsonURL:
"https://raw.githubusercontent.com/plotly/plotly.js/master/dist/topojson/",

[ajuric]

You can redeploy/upgrade your installation to use local packages instead of cdns with:

...
ui:
  offline: true
...

@bastianerh Does this means Polyaxon web will not be deployed/available?

[bastianerh]

@ajuric The UI will be available, the only difference is that it will serve all js packages and vendors from Polyaxon server instead of the CDNs.

[ajuric]

@bastianerh Cool, thank you a lot! :)

Is there any reason then why not always setting the "offline: true", to avoid problems like these? Asking because I handle our PLX deployment and would like to minimize my involvement there, but also wouldn't like to miss all the "good features" or don't "good practices" for deployment?

[ajuric]

I see, thanks! 👍

[Syakyr]

Since the CDNs are back up, I'll close the issue. Hopefully if the CDNs are down again, this issue can be used as a reference.