Package: collective.cdn.core
Table of ContentsCDN Support for PloneOverviewRequirementsInstallationUsageKnown IssuesSponsoringCreditsChangelogCDN Support for PloneOverviewThis package implements a very basic CDN support for Plone sites. Resources
registered at the portal registries (Styles, Scripts and KSS) can be
delivered by specialized servers on different hostnames.Also this package implements an experimental approach to serving image
content from a CDN. We plan to improve this feature in future releases.You must add a provider package in order to use CDN Support!Available provider packages are:AlternateHostname - collective.cdn.alternatehostnameCoral Networks - collective.cdn.coralMultipleHostnames - collective.cdn.multiplehostnamesRequirementsPlone 3.3.x (http://plone.org/products/plone)Plone 4.0.x (http://plone.org/products/plone)Plone 4.1.x (http://plone.org/products/plone)Plone 4.2.x (http://plone.org/products/plone)InstallationTo enable this product,on a buildout based installation:Edit your buildout.cfg and addcollective.cdn.coreto the list of eggs to install[buildout]
...
eggs =
    collective.cdn.coreIf another package depends on the collective.cdn.core egg or
includes its zcml directly you do not need to specify anything in the
buildout configuration: buildout will detect this automatically.After updating the configuration you need to run the ‘’bin/buildout’’,
which will take care of updating your system.Go to the ‘Site Setup’ page in the Plone interface and click on the
‘Add/Remove Products’ link.Choose the product (check its checkbox) and click the ‘Install’ button.Uninstall – This can be done from the same management screen, but only
if you installed it from the quick installer.Note: You may have to empty your browser cache and save your resource
registries in order to see the effects of the product installation.UsageCDN settingsAfter installing this package, go to the ‘Site Setup’ page in the
Plone interface and click on the ‘CDN Configuration’ link.In this page you can choose which registries will use the CDN settings
by clicking the respective checkboxes.Also you must choose a provider – added by specific packages as
collective.cdn.coral – and then inform hostnames, port and a path to
be used by the provider.Basic exampleThe simplest configuration would be possible by installing the
collective.cdn.alternatehostname, which will enable you to add a alias
hostname to your site.This configuration allows you to add a alternate hostname as your CDN,
for example, using the alias localhost for a site running on 127.0.0.1.Known IssuesServing javascripts resources from a server not on the same domain as
the main site could break some Plone features as this would fail thesame origin policy for javascript.Serving images from CDN still is considered a experimental feature as
it only supports images which are referenced through thetagmethod
of the Archetypes ImageField. We plan to support other content types
in the future.SponsoringDevelopment of this product was sponsored bySimples Consultoria.CreditsSimples Consultoria (products at simplesconsultoria dot com dot br) -
ImplementationChangelog0.6 (2012-08-01)Refactor tests to use plone.app.testing [ericof]PEP 8 cleanup [ericof]Import IVocabularyFactory from zope.schema.interfaces. [ericof]0.5 (2011-02-21)Experimental support for Archetypes ImageField [ericof]Support for resource registries items [ericof]Initial release of collective.cdn.core [ericof]