As the public dir usually contains stylesheets and javascript files as
well as images, which might change with every release, I like to have
the public dir in current.
But we have a static image pool of 1.5 GB, which we do even manage in
the same SVN like our codebase.
I've a separate task to update the image pool to a subdirectory in the
shared/public dir (#{shared_path}/public/images/cimg)
task :checkout_images, :roles => :web do
run("svn co svn+ssh://svn.SERVER/PROJECT/trunk/cimg #{images_dir}/
cimg")
symlink_cimg
end
and another one for symlinking it from shared to current:
task :symlink_cimg, :except => { :no_release => true } do
run("ln -nfs #{images_dir}/cimg #{release_path}/public/images/cimg")
end
where images_dir points to "#{shared_path}/public/images"
The two tasks check out the separate image pool SVN repository to our
cimg subdirectory in shared/public and then symlink it to current/
public.
That gives us the best of both worlds - deployment of application
icons, javascripts and stylesheets while having an asyncronous way of
deploying updates in the static image pool.
Matthias
On 2 Jun., 09:40, sol <[EMAIL PROTECTED]> wrote:
> Hey,
>
> I want to upload my public/ dir into my shared dir and symlink to it,
> to keep all my assets.
>
> However, capistrano does handle the public/ directory in it's own way,
> when creating the system symlink, so my question is:
>
> What is the reason that public/ is not inside shared by default?
> Whats the common way to achieve the behavior I want (keeping all my
> uploaded assets) ?
>
> Thank you,
> Christoph
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
