Hi Tony,
Look into Ryan Bates Railscasts... there is one talking about
Capistrano (and his tricks when dealing with images and other site
specific data).
http://railscasts.com/episodes/133-capistrano-tasks
Jean-Marc
http://m2i3.com/blog/jean-marc
Jean-Marc (M2i3.com) wrote:
Hi Tony,
Look into Ryan Bates Railscasts... there is one talking about
Capistrano (and his tricks when dealing with images and other site
specific data).
http://railscasts.com/episodes/133-capistrano-tasks
Jean-Marc
http://m2i3.com/blog/jean-marc
Hi
Hi Tony... the rm line is only there for the release_path directory
which either will have the symlink OR an empty directory that was
checked-out from git. If the developers wants a few test images in
git for testing you can do that but need to remove that when it is
deployed to prod before you
Freddy Andersen wrote:
Hi Tony... the rm line is only there for the release_path directory
which either will have the symlink OR an empty directory that was
checked-out from git. If the developers wants a few test images in
git for testing you can do that but need to remove that when it is
But #{release_path}/public/images/users will still be symlinked to
#{shared_path}/users #{release_path}/public/images/users and the r
option will remove all files in that directory so I would just remove
the r option and you should be OK. No???
On Nov 3, 11:10 am, Freddy Andersen [EMAIL
Tim McIntyre wrote:
But #{release_path}/public/images/users will still be symlinked to
#{shared_path}/users #{release_path}/public/images/users and the r
option will remove all files in that directory so I would just remove
the r option and you should be OK. No???
Maybe this makes some
Tim McIntyre wrote:
I'd watch out for the rm -rf #{release_path}/public/images/users
line. I think that would remove all your images.
Hi Tim,
Thanks for the tip. I've been busy so I haven't tried to do this just
yet but I'm sure it would remove the images. The idea is to move the
I think, if I'm understanding your situation correctly, you want to
symlink your user image directories into somewhere under your /home/
#{user}/public/#{application}/shared directory.
The shared directory created by capistrano on your staging server
does not change from release to release.
That is how Capistrano is supposed to work. You checkout new code from
your repo and the current link is replaced with the latest checkout in
releases/datestamp.
Just like Tim said when you have content that needs to be shared
between releases you need to put that somewhere else LIKE the shared
Hi Tim Freddy,
Thanks for the prompt and insightful replies. I'm glad I got it clear
that this IS how Capistrano is supposed to work and that I shouldn't try
to fight it much.
I wouldn't have even imagined I should have to symlink to get this to
work. I'll give it a try and come back if I
10 matches
Mail list logo
