On Feb 12, 2007, at 9:03 AM, rumplyminz wrote:

> Jamis,
>
> Thanks for the answer (I figured it was easy) and also the suggestion
> on the symlink.  That might work, and I will check it out, and let you
> know!
>
> Also, are you using a newsreader, or just gmail, for the google
> groups?

Neither. I'm just subscribed to the list using my regular email  
address. Why do you ask?

- Jamis

>
> Thanks!
> Josh
>
> On Feb 12, 10:53 am, Jamis Buck <[EMAIL PROTECTED]> wrote:
>> Josh,
>>
>> You can do "#{previous_release}/...." to get at the release prior to
>> the one most recently deployed.
>>
>> However, I wonder if you could still make this work with symlinks.
>> What if you put the Tiny_MCE stuff in:
>>
>>    ./public/system/tiny_mce/plugins/filemanager/files
>>
>> And then made a symlink from
>>
>>    ./public/javascripts/tiny_mce
>>
>> to
>>
>>    ./public/system/tiny_mce
>>
>> You could create that symlink automatically, on each deploy, via
>> after_update_code. Would that work?
>>
>> - Jamis
>>
>> On Feb 12, 2007, at 8:40 AM, rumplyminz wrote:
>>
>>
>>
>>> Hi all,
>>
>>> I am using a php plugin called Tiny_MCE with the file manager  
>>> enabled
>>> for one of my rails apps.  It needs to have the location for the  
>>> files
>>> be in ./public/javascripts/tiny_mce/plugins/filemanager/files/ in
>>> order for the file manager to work correctly.  I tried using a  
>>> symlink
>>> to make this point to ./public/system/files (which is a symlink that
>>> allows me to carry uploads, etc over from build to build) but the  
>>> file
>>> manager won't work with the symlink due to how php is reading the
>>> absolute file path from the symlink.
>>
>>> Anyway, I do need to make sure these files are carried over from  
>>> build
>>> to build.
>>
>>> Is there an easy way to get the most recent capistrano build
>>> directory, so that I can recursively copy that directory over?
>>
>>> Cheers,
>>> Josh
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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