Tag Archives: cdn

Setting up WordPress behind Amazon Cloudfront

You all know that feeling (well, I hope you do!) that when a spike in traffic occurs on your WordPress site, that the miniature server you have it running on very quickly runs out of resources. Apache’s good like that. Taking up all the resources with its large number of processes consuming oodles of memory each. How on earth can you possibly fix it, especially when you’re running on a tight budget and upgrading the server for that once-in-a-blue-moon you get a spike in traffic? Well, Amazon Cloudfront to the rescue!

Continue reading “Setting up WordPress behind Amazon Cloudfront” »

Amazon Web Services – A Guide to Implementation

I realise that I’ve been neglecting my blog for a while now, with my last post published at the end of March. Quite frankly, I’ve not had anything interesting to write about. However, career starting pastures new, I’m starting to have interesting things to write about again. Over the course of time, I’ll probably post a lot of stuff about Amazon Web Services (AWS), Zend Framework, amongst other things. Today’s babble though is about implementing AWS as your core hosting infrastructure, and the benefits and downsides to it. I’ll also post my findings about the best way (in my opinion) to implement certain requirements.

Continue reading “Amazon Web Services – A Guide to Implementation” »

Amazon S3 CDN distribution for Menalto Gallery 3 v2.1 released

Announcing the release of the Amazon S3 v2.1 module for Gallery 3. A few changes are presented here;

  • Firstly, started using double digits for version numbers so I can create minor revisions
  • Added fields to database to store MD5 hashes of files. These are used to match the MD5 hash of the local file, and what the module thinks is uploaded, and also for comparison with S3 itself (which provides an MD5 hash when asked for bucket info)
  • Re-visited re-sync task. Taken out “emptying bucket” code (as there’s really no need it seems), and simplified the whole process, allowing the module to compare the MD5 hash of the local file against the same file path on S3, and upload/overwrite if they’re different, or if the module doesn’t believe the file has been uploaded.
  • Resolved issues of moving entire albums from one location to another and files disappearing. This invoked a re-visit of the move code as well and cleaned up quite a lot of unnecessary stuff.

Download the latest version here: Amazon S3 for Gallery 3 : v2.1 (md5: )
As always, direct comments, feedback and bug reports to the module’s official thread on Gallery’s forums.

Note: I will no longer be updating the gallery3-contrib git repository as it’s just easier to update my site than it is to update a load of other places and wait for pulls to be granted. Sorry.

Amazon S3 CDN distribution for Menalto Gallery 3 v2 BETA

I just posted beta version 2 of this module on the G3 forum. As I wrote there, but will write here too, here’s the changelog:

  • Access Key, Secret Key, and Bucket name validation
  • Ability to upload only thumbs, resizes, fullsizes, or any combination of the 3
  • Resolved compatibility with crossdomain issue in album organize. Thumbs are now vended from the local server as crossdomain blocks flash from loading these (though CoolIris is not affected, I’m not sure why)
  • Ability to (if used with updated Scheduler module (linked below)) sync and upload items to S3 via a cron job rather than “there-and-then”. This resolves the upload progress bar stalling/freezing/browser crashing issues while waiting for server to upload to S3
  • Spelling changes
  • Updated S3 lib to ignore SSL certificate mismatches. This resolves communicating data to S3 via SSL if required. The warning is still in place on the admin page though, as you may or may not still run into issues using SSL
  • Added support to move items around S3 when items are moved around the G3 installation. When images are now moved from album to album, the item is moved in S3 accordingly. Images are also updated on S3 when rotated. Haven’t tested this with the Watermark module yet though.
  • Resolved problem validating Access Key/Secret Key/Bucket Name info on first/new install of module (not affecting upgraders from version 1 of this module)
  • Resolved issues with Organize crashing as (0 of x items completed) when moving items between albums.
  • (Potentially) resolved issues that prevented Server Add module from working correctly.

Yet to come:

  • Use S3 for primary storage (useful for low-storage hosting accounts) – This is pegged for v3

You can download it here: Amazon S3 for Gallery 3 : v2.1 (md5: )

Please direct all feedback and bug reports to the thread on G3′s forum here.

Amazon S3 CDN distribution for Menalto Gallery 3

Announcing a new module for Gallery 3 by Bluespider Technical Solutions: Amazon S3 CDN

This module integrates deeply into the Gallery 3 code, and seamlessly redirects your web clients to your Amazon S3 bucket for content, leaving your web server only the task of serving up the Gallery 3 HTML pages. This module also hooks into item upload, move and delete events and copies, moves or deletes content from your S3 bucket as and when you create, move or delete it.

For galleries with content pre-added, we provide a task which performs a syncronisation between Gallery 3 and the S3 bucket for all content and album thumbnails, resizes and full sized images that would have otherwise been served up by Gallery 3.

Download it here: Amazon S3 for Gallery 3 : v2.1 (md5: )
Gallery Codex page here
HISTORICAL Support Forum Thread here
Use the comment box at the bottom of this page for support, or contact me directly. I’d rather you commented in the open forum though, since this is open source and all :)

Changelog
26th November 2010 :: Version 1 :: Initial release.
19th December 2010 :: Version 2 (beta)

  • Key, and Bucket name validation
  • Ability to upload only thumbs, resizes, fullsizes, or any combination of the 3
  • Resolved compatibility with crossdomain issue in album organize. Thumbs are now vended from the local server as crossdomain blocks flash from loading these (though CoolIris is not affected, I’m not sure why)
  • Ability to (if used with updated Scheduler module (linked below)) sync and upload items to S3 via a cron job rather than “there-and-then”. This resolves the upload progress bar stalling/freezing/browser crashing issues while waiting for server to upload to S3
  • Spelling changes
  • Updated S3 lib to ignore SSL certificate mismatches. This resolves communicating data to S3 via SSL if required. The warning is still in place on the admin page though, as you may or may not still run into issues using SSL
  • Added support to move items around S3 when items are moved around the G3 installation. When images are now moved from album to album, the item is moved in S3 accordingly. Images are also updated on S3 when rotated. Haven’t tested this with the Watermark module yet though.
  • Resolved problem validating Access Key/Secret Key/Bucket Name info on first/new install of module (not affecting upgraders from version 1 of this module)
  • Resolved issues with Organize crashing as (0 of x items completed) when moving items between albums.
  • (Potentially) resolved issues that prevented Server Add module from working correctly.

20th January 2011 :: Version 2 Final :: Release
29th January 2011 :: Version 2.1

  • Firstly, started using double digits for version numbers so I can create minor revisions
  • Added fields to database to store MD5 hashes of files. These are used to match the MD5 hash of the local file, and what the module thinks is uploaded, and also for comparison with S3 itself (which provides an MD5 hash when asked for bucket info)
  • Re-visited re-sync task. Taken out “emptying bucket” code (as there’s really no need it seems), and simplified the whole process, allowing the module to compare the MD5 hash of the local file against the same file path on S3, and upload/overwrite if they’re different, or if the module doesn’t believe the file has been uploaded.
  • Resolved issues of moving entire albums from one location to another and files disappearing. This invoked a re-visit of the move code as well and cleaned up quite a lot of unnecessary stuff.