I'm using Capistrano 2 with subversion and I have it ignore the
contents of tmp/*. It turns out that for some reason Rails won't try
to create the tmp/cache or tmp/sessions folder, and even if it did,
Capistrano would not automatically symlink those to the shared folder.

So here's my question: shouldn't Capistrano automatically try and
symlink everything on tmp to the shared folder? Or is it expected that
whenever I roll out a new revision I loose all my sessions and cached
pages (both on tmp/cache and public). If that's the case, should I
simply set subversion not to ignore tmp/* but instead tmp/cache/*, tmp/
sessions/*?

Also, in a not so related question, why isn't the remote_cache
deployment strategy the default one? Isn't it much better than
checking out the entire code every time?

Thanks in advance


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to