A content delivery network or content distribution network (CDN) is a system of computers containing copies of data, placed at various points in a network so as to maximize bandwidth for access to the data from clients throughout the network. A client accesses a copy of the data near to the client, as opposed to all clients accessing the same central server, so as to avoid bottleneck near that server. Content types include web objects, downloadable objects (media files, software, documents), applications, real time media streams, and other components of internet delivery (DNS, routes, and database queries).
In the performance admin panel:
Without any server configuration, you can from the admin panel, pick Google as the CDN for your jQuery files.
You can also use Amazon CloudFront.
With a little server configuration, you can also use your own server as a CDN.
- Make your server have two domains (ex.: tiki.org and cdn.tiki.org)
- This can be done using "parked domains" (not add-on) on shared hosting
- Enter your CDN (ex: cdn.tiki.org)
If you are already on a sub-domain, it could be doc.tiki.org and cdn.doc.tiki.org
This will improve your YSLOW scores if you tell your YSlow that cdn.doc.tiki.org is in the official list of CDNs.
CORS headers must be enabled for CDN to work properly - check .htaccess (Apache) or web_config (IIS).
- New for 16.1
- As of 2016-12-13, there is no option for NGINX.
The interface for CloudFront
Coral is a free peer-to-peer content distribution network, comprised of a world-wide network of web proxies and nameservers. http://www.coralcdn.org/
To use, put as CDN:
where "tiki.org" is indeed replaced with your real domain.
Then, some of the static content like images and css/js files will be delivered by the coral network.