EngineYard : Segregating the code & assets

Question

Am using EngineYard to host my Rails 3.2 app. This application allows users to post images/assets. I save them in the public directory (using Paperclip Gem). Now, my problem is that - with a new deployment, I am having to manually copy over the assets to the CURRENT version.

Though, I could use AmazonS3, I still want to figure out if there is a way in EngineYard which lets me save/serve the assets from a different directory than the code, say /data/assets.

Please, let me know if you see any other alternate implementations too.

score 1 · Answer 1 · answered Jun 14 '12 at 07:39

1

Typically your structure would look like

/data
  myapp/
    shared/
      images 
    releases/
      20120613000000
      20120601000000
      ...
    current (symlink to one of the releases)

When you deploy, you symlink public/images to shared/images and so your images always get stored in a non release dependant location.

I would encourage you to use something like s3: you'll make things a lot easier for when you want to host the app on multiple instances.

answered Jun 14 '12 at 07:39

Frederick Cheung

83,189
8
152
174

Should I manually SSH into the server & create the symlink after every deployment ? Or, Is there a script that I need to edit ? – Satya Kalluri Jun 14 '12 at 08:03
No, do this in your deploy.rb (I assume you're using capistrano) – Frederick Cheung Jun 14 '12 at 08:35

EngineYard : Segregating the code & assets

1 Answers1