Install
Works with Drupal: 8.xUsing Composer to manage Drupal site dependencies
Alternative installation files
Release notes
After 10 weeks of RCs, here's the first stable release!
The CDN module is fully ported to Drupal 8. It is much simpler to use (just look at the UI). It has less overhead (the UI is in a separate module, the altering of file URLs has far simpler logic). It has lower technical complexity (File Conveyor support was dropped, it no longer needs to detect HTTP vs HTTPS: it always uses protocol-relative URLs, less unnecessary configurability, the farfuture functionality no longer tries to generate file and no longer has extremely detailed configurability).
In other words: the CDN module in Drupal 8 is much simpler. And has much better test coverage too. (You can see this in the tarball size too: it's about half of the Drupal 7 version of the module, despite significantly more test coverage!)
- all the fundamentals
-
- the ability to use simple CDN mappings, including conditional ones depending on file extensions, auto-balancing, and complex combinations of all of the above
- DNS prefetching
- a simple UI to set it up — in fact, much simpler than before!
- changed/improved
-
- the CDN module now always uses protocol-relative URLs, which means there's no more need to distinguish between HTTP and HTTPS, which simplifies a lot
- the UI is now a separate module (fixes #1784432: Version 3.0: move UI of CDN module into a cdn_ui module)
- the UI is optional: for power users there is a sensible configuration structure with strict config schema validation
- complete unit test coverage of the heart of the CDN module, thanks to D8's improved architecture
- DNS prefetching using headers rather than tags in
<head>, which allows me to use a much simpler/cleaner Symfony response subscriber - tours instead of advanced help (fixes #1753174: Dependency for advanced_help module), which very often was ignored
- there is nothing to configure for the SEO (duplicate content prevention) feature anymore
- nor is there anything to configure for the
Forever cacheable files
feature anymore (namedFar Future expiration
in Drupal 7), and it's a lot more robust
- removed
-
- File Conveyor support
- separate HTTPS mapping (also mentioned above)
- all the exceptions (blacklist, whitelist, based on Drupal path, file path…) — all of them are a maintenance/debugging/cacheability nightmare
- configurability of SEO feature
- configurability of unique file identifiers for the
Forever cacheable files
feature - testing mode
Contributors (3)
mcdruid, Wim Leers, ashleyhazle
Changelog
Issues: 2 issues resolved.
Changes since 8.x-3.0-rc2:
