Cloudinary Blog

Engine Yard add-on for cloud-based image management

When we first started working on Cloudinary we had a very simple goal in mind - offer a complete alternative to a set of rudimentary, repetitive, universally common web dev tasks. Tasks related to a website's image management needs.
 
As a web developer, you surely found yourself spending considerable time performing the same routine asset management tasks over and over again. Managing image uploads, transformations, manipulations, optimizations, caching and back-ups. Configuring a fast, highly available asset delivery solution. Same tasks, over and over again.
 
Cloudinary was built to streamline all of the above and we're very proud with what we've accomplished with Cloudinary so far. What started as a simple concept, turned out to be a great service that completely solves all your online image management tasks.
 
The fact that took us by surprise was the diversity of frameworks used by our customers. It sometimes felt that each new user has utilized his own web development stack. Ruby developers using Rails or Sinatra, PHP developer using one of the countless PHP frameworks, Python and Django developers, Node.js, Perl, Java, ASP, .NET, iOS, Android and many others.
 
It turns out that as complicated it is to build a highly scalable, highly usable service like Cloudinary, it's still only half of the story. The other half is offering our users a solution that is easy to integrate with their web dev platform of choice. 
 
Lately, we've been hard at work adding client side Cloudinary integration libraries for every major web dev platform and programming language. We've also kept a close eye on the state-of-the-art platform-as-a-service solutions that offered their users a single click integration solutions for a vast array of cloud-based services. Today, we've taken another important step on making Cloudinary even more accessible and easy to use.
 
Without further ado, we're happy to announce our partnership with Engine Yard. 
 
Engine Yard is a senior player in the PaaS field and one of the pioneers of the approach that took cloud computing a step forward: developers take care of the application development only, while Engine Yard takes care of the production platform. You no longer need to manage production servers and complex database architecture. Engine Yard is unique in this field in providing a full management solution for large scale platforms and high-end sites and applications.
 
 
With Engine Yard you have your application deployed in the cloud. Together with Cloudinary, your asset management is also moved into the cloud: upload images, automatically perform smart image resizing, cropping, overlay, watermark, apply effects, rotations, format conversions, without installing any complex software. All your images are then seamlessly delivered through a fast CDN, optimized and using industry best practices. Cloudinary offers comprehensive APIs and administration capabilities and is easy to integrate with new and existing web and mobile applications.
 
Together with Engine Yard, Cloudinary offers a very useful solution for a wide array of use-cases from simple websites, through early stage startups to large scale enterprise applications. If you are already an Engine Yard user, simply add Cloudinary's add-on to your Ruby, PHP and Node.js applications. Cloudinary’s account setup is done automatically for you and billing is handled through your standard Engine Yard payment method. Cloudinary offers a free Starter plan with plenty of room to grow, making it very straightforward to try it out.
 
 

Engine Yard users - want to start using Cloudinary?

  • Go to https://cloud.engineyard.com/addons or navigate to 'Add-ons' in Engine Yard Cloud and click on Cloudinary and start managing your images in the cloud!
  • Engine Yard automatically sets up the correct settings for using your Cloudinary account using the CLOUDINARY_URL variable. 
Ruby on Rails users - simply add the ey_config GEM to your project and add an initializer for Cloudinary's settings:
Cloudinary.config_from_url(EY::Config.get(:cloudinary, 'CLOUDINARY_URL'))
We will soon add additional documentation and sample code for simplifying the Cloudinary - Engine Yard integration even further. Any feedback on our new image management add-on for Engine Yard would be highly appreciated!

Recent Blog Posts

Responsive Images Guide, Part 1: What does it mean for an image to be “responsive”?

“Responsive.” Where did that term come from, anyways?

In his sea-changing essay, Responsive Web Design, Ethan Marcotte explained:

Recently, an emergent discipline called “responsive architecture” has begun asking how physical spaces can respond to the presence of people passing through them. Through a combination of embedded robotics and tensile materials, architects are experimenting with art installations and wall structures that bend, flex, and expand as crowds approach them. … rather than creating immutable, unchanging spaces … inhabitant and structure can—and should—mutually influence each other.

Read more
Automatically deliver the best image format to the browser

One of the main optimization challenges for website and mobile developers is how to display sufficiently high quality images to their visitors while minimizing the image file size. A smaller image file size can lead to faster load times, reduced bandwidth costs and an improved user experience. The problem is that reducing the file size too much may lead to a lower image quality and could harm visitor satisfaction. Delivering an optimized image with just the right balance between size and quality can be quite tricky.

Read more
Three different ways to do progressive JPEG encoding

There are two different kinds of JPEG images: progressive JPEGs and non-progressive JPEGs. These categories have nothing to do with the JPEGs’ political beliefs. They’re all about the order in which they’ve been encoded.

Read more