nopCommerce CDN Plugin

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
11 years ago
Hi,

We have created a free CDN Plugin for nopCommerce - nopAccelerate CDN. The plugin extend picture service to use external host name defined in plugin settings.

Once configure, it will then load pictures from those hostnames / CDN URL.

Features of nopAccelerate CDN Plugin

- Supports any CDN that support Pull Zone
- Easy to Install & Configure
- Load all Product, Category & Manufacturer images from CDN
- Support Multiple Hostnames as CDN URL


Please read more about the plugin at http://www.nopaccelerate.com/nopcommerce-plugins/nopaccelerate-cdn/

To look at Demo: http://demo.nopaccelerate.com/

CDN Plugin Installation Guide: http://www.nopaccelerate.com/wiki/installing-configuring-nopaccelerate-cdn-plugin/

This plugin is released for free by courtesy of nopAccelerate. Please feel free to visit us for more nopCommerce Performance Optimization plugins & nopCommerce Development services.

Please also feel free to visit our blog at http://www.nopaccelerate.com/blog/ ! :)
11 years ago
Hi Krunal,

Good job!
11 years ago
a.m. wrote:
Hi Krunal,

Good job!


Thank you Andrie!
11 years ago
Hi,

Pls feel free to request a new feature here.... And provide your suggestions / idea to improve the same...

thanks
Krunal
10 years ago
The CDN Plugin has been upgraded to support nopCommerce 3.0 with multi-store version.

You can download it from here: http://www.nopaccelerate.com/nopcommerce-plugins/nopaccelerate-cdn/

Thanks
10 years ago
We have added following features to the Plugin.

- Support for custom CDN url for Stylesheets & Java Script Files
- Support for CDN Bundling
- Support for SSL on CDN Urls
- Ability to not use CDN Urls on pages that are secured with SSL

It will be available soon for download.

Thanks
10 years ago
Hi Krunal
As a delivery method works great and thanks I was half way through doing my own version and has saved me the hassle.

But I've always used AWS Cloudfront as my CDN and it works well but the process of adding products and pictures does not seem to work so well which I imagine in a generic form might be tricky any plans to work on this?
Thanks
Rob
10 years ago
playblue wrote:
Hi Krunal
As a delivery method works great and thanks I was half way through doing my own version and has saved me the hassle.

But I've always used AWS Cloudfront as my CDN and it works well but the process of adding products and pictures does not seem to work so well which I imagine in a generic form might be tricky any plans to work on this?
Thanks
Rob


Hi Rob,

Can you please explain on what doesn't seem to work, so we can check and update you with the suggestions.

Thanks,
Krunal
10 years ago
Hi
The plugin works well in delivering the images from the CDN (in my case AWS Cloudfront).
I was testing the process to add a new image to a product using the admin screen in the nop instance and it failed here, not sure if there has been any implementation here as not really sure how it could work because no credentials are available to the plugin to write to the CDN.

Can you tell me the process you suggest to add ongoing images to the CDN?

The admin screen is trying to present the image from the CDN too.
Thanks
Rob
10 years ago
playblue wrote:
Hi
The plugin works well in delivering the images from the CDN (in my case AWS Cloudfront).
I was testing the process to add a new image to a product using the admin screen in the nop instance and it failed here, not sure if there has been any implementation here as not really sure how it could work because no credentials are available to the plugin to write to the CDN.

Can you tell me the process you suggest to add ongoing images to the CDN?

The admin screen is trying to present the image from the CDN too.
Thanks
Rob


Hi, The plugin does not write any image or other resources to the CDN (this is popularly known as Push Zone CDN). So it is not working as you expect. The plugin actually working in very different way by utilizing Pull Zones.

Content Delivery Networks come in two flavors: push zones and pull zones. While a pull zone CDN is thought to be slightly less efficient than a push zone, the latter requires you to maintain and regularly update a master copy of your content on a separate server. As a result, configuring a push zone CDN is very complicated and almost always requires more storage space than a pull zone CDN.

A Pull Zone is what is needed to utilize the HTTP Caching type of CDN. The name Pull Zone came from the technique used, as the CDN will “Pull” the static assets from your website to cache it and serve it from CDN Network.

This means that when you request a resource from CDN URL, CDN will check for that resource in its cache. If its available, it will serve it from there. If it's not available, it will request the resource from your website, serve the request also cache it for future. The next request to that resource will be served from the CDN's cache.

You are not seeing new images being added to your CDN. This can be caused only if your origin url is not reachable by the cdn, or the image was not created on your website at first place.

Are you able to open that images directly from your website url? If so, there is something wrong with the pull zone configuration with your CDN provider.  If not, the issue is either with folder permissions or something else. The starting point is to check the application error log to get an idea on what could be wrong here.

Moreover, if you are not sure on how to configure pull zones with Cloud Front, have a look at this resource http://anything-digital.com/blog/infrastructure/use-amazon-cloudfront-to-instantly-improve-the-performance-of-your-joomla-web-site.html which might be helpful to you.

If you're not able to fix it, pls feel free to update it here.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.