Does anyone have any experience getting RMagick up and running on a Media Temple (gs)? I'm still not sure if I need to build GraphicsMagick myself, and if so, how because I don't have root access???
on 2007-03-07 22:30
on 2007-04-15 14:26
This should not be a problem. I jusy built ffmeg (for use with gallery2) and it worked fine. you just need the to ssh in...
on 2007-04-15 23:58
Hi, On 08/03/07, Sean J. Rucker <email@example.com> wrote: > > Does anyone have any experience getting RMagick up and running on a > Media Temple (gs)? > > I'm still not sure if I need to build GraphicsMagick myself, and if > so, how because I don't have root access??? I too am on MT on their GS plan. They have a gem which you can install and all works well, until you actually use it. RMagick is known to be very leaky and loading a single large image file (3mb) will bring down your container (I only have 64mb). There's a couple of alternatives, Image Science (http://seattlerb.rubyforge.org/ImageScience.html) is built specifically because of this memory issue. Alas, it requires Free Image which is not a ruby program so there's no gem and it's also a pain to get going. I've put in for a feature request for Image Science to be installed. In the meantime, I'm just going to be shelling out and run mogrify (http://www.imagemagick.org/script/mogrify.php) -- Cheers, Serdar Kýlýçhttp://weblog.kilic.net/
on 2007-09-02 16:50
This is a bump for anyone using (gs) and any kind of image processing... I've yet to get a response from MT about whether or not image_science is available, but in the meantime I'm just using MiniMagick, which is running very well. Rick Olson's excellent attachment_fu has a processing backend for MiniMagick, so it's a simple switch to use that instead. Just install the MiniMagick gem on your (gs) account, set :processor => :MiniMagick, and off you go! MiniMagick basically wraps mogrify, so it should be much friendlier to memory than RMagick. Matt