|
|
|
> This will require an update after we switch the CDN to Rackspace.
|
|
|
|
|
|
|
|
As of MathJax 1.1 we are maintaining a public installation on a Content Delivery Network (CDN) for several reasons:
|
|
|
|
|
|
|
|
* Users of software such as Blogger have no server access and thus can't install MathJax themselves. They could, however, point to a publicly hosted version of MathJax.
|
|
|
|
* By hosting MathJax, we can control versioning and patches carefully, thereby increasing reliability
|
|
|
|
* Because of both reduced latency and caching, CDN hosting will improve performance for most users
|
|
|
|
* We can easily collect statistics about pages and sites using the hosted version of MathJax
|
|
|
|
|
|
|
|
We have selected CloudFront, part of the Amazon Web Services as our CDN service.
|
|
|
|
|
|
|
|
### Quick Guide to Updating CDN Content
|
|
|
|
|
|
|
|
MathJax CDN content is served from the `cdn.mathjax.org` domain. The source of this data (the CloudFront origin) is our main mathjax.org server. Contact Robert for information for access information. The CDN content is located under
|
|
|
|
|
|
|
|
`./webapps/dist/mathjax/...`
|
|
|
|
|
|
|
|
There is a README file in that directory with detailed information. However, the basic set up is that each versioned release on the CDN corresponds to a subdirectory, and each of those subdirectories is an independent clone of the canonical mathjax Git repo on GitHub. Thus, to update CDN content, one merely updates content in the appropriate release directory by using git to pull content from GitHub.
|
|
|
|
|
|
|
|
CloudFront will automatically pick up changes in origin data, and propagate them throughout the CDN in about 16 mintues. |
