I’m just implementing an internal dashboard using Bokeh. The site is SSL-only. Unfortunately, when I attempt to access the CSN via SSL, it returns a certificate that doesn’t match the domain.
(e.g. accessing https://cdn.pydata.org/bokeh-0.6.1.min.css). Chrome summarizes it nicely as “This server could not prove that it is cdn.pydata.org; its security certificate is from a248.e.akamai.net”.
Is there a convenient work-around for this? I could pull the static files into my own server, but then I’d be faced with having to keep them up-to-date/synced with each release. Can the Bokeh server offer up the installed version on access to something generic, like /static/bokeh.min-css?
Perhaps Bokeh would consider using a CDN service that support user SSL certificates (Akamai does, but unsure if that passes through to Rackspace or not).
Is there a recommended way to get the latest version of those files from the site-packages installation (for example, my Tornado server could check for the existence of the files in the static web folder and if missing, copy them from the package…)