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

Hipcamp Optimizes Images and Improves Page Load Times With Cloudinary

When creating a website that allows campers to discover great destinations, Hipcamp put a strong emphasis on featuring high-quality images that showcased the list of beautiful locations, regardless of whether users accessed the site on a desktop, tablet, or phone. Since 2015, Hipcamp has relied on Cloudinary’s image management solution to automate cropping and image optimization, enabling instant public delivery of photos, automatic tagging based on content recognition, and faster loading of webpages. In addition, Hipcamp was able to maintain the high standards it holds for the look and feel of its website.

Read more
New Image File Format: FUIF: Why Do We Need a New Image Format

In my last post, I introduced FUIF, a new, free, and universal image format I’ve created. In this post and other follow-up pieces, I will explain the why, what, and how of FUIF.

Even though JPEG is still the most widely-used image file format on the web, it has limitations, especially the subset of the format that has been implemented in browsers and that has, therefore, become the de facto standard. Because JPEG has a relatively verbose header, it cannot be used (at least not as is) for low-quality image placeholders (LQIP), for which you need a budget of a few hundred bytes. JPEG cannot encode alpha channels (transparency); it is restricted to 8 bits per channel; and its entropy coding is no longer state of the art. Also, JPEG is not fully “responsive by design.” There is no easy way to find a file’s truncation offsets and it is limited to a 1:8 downscale (the DC coefficients). If you want to use the same file for an 8K UHD display (7,680 pixels wide) and for a smart watch (320 pixels wide), 1:8 is not enough. And finally, JPEG does not work well with nonphotographic images and cannot do fully lossless compression.

Read more
 New Image File Format: FUIF:Lossy, Lossless, and Free

I've been working to create a new image format, which I'm calling FUIF, or Free Universal Image Format. That’s a rather pretentious name, I know. But I couldn’t call it the Free Lossy Image Format (FLIF) because that acronym is not available any more (see below) and FUIF can do lossless, too, so it wouldn’t be accurate either.

Read more