[Radiant] RadiantOnRails extension

[Sean Cribbs]

Why not keep Radiant in vendor/radiant?  Then the startup scripts would 
require less modification.

Sean

Matt Parrish wrote:
> Yes, it seems to me like that is the goal.  Currently, Radiant takes  
> control of the files in config/ to do its initialization.  It seems  
> like we would want to keep the Rails files as is, and do the  
> initialization in plugins/radiant/init.rb.  I haven't looked at it  
> yet, but I'm guessing there will be a few challenges to getting this  
> to work properly.  One challenge I immediately see is getting  
> Radiant's routes to coordinate with the Rails ones in config/routes.rb.
>
> Matt Parrish
> http://www.pearware.org
>
>
> On Jun 1, 2007, at 9:17 PM, Meekish wrote:
>
>   
>> Loren Johnson wrote:
>>     
>>> You're absolutely right, sorry I hadn't looked closely enough.
>>>
>>> You could gem install Radiant and generate an instance and then merge
>>> the necessary bits from the environment.rb it generates into your
>>> existing app.
>>>
>>> If I get a chance I'll try and determine what those necessary bits
>>> are later today and email back what I learn.
>>>
>>> Loren
>>>       
>> So is the goal at this point to make it possible to install Radiant  
>> as a
>> plugin with the folder structure that John laid out?
>>
>> plugins/
>>    radiant/
>>      init.rb
>>      lib/
>>      vendor/
>>        radiant/  <<< an svn:external to trunk/radiant
>>
>> -- 
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> Radiant mailing list
>> Post:   Radiant at lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>     
>
> _______________________________________________
> Radiant mailing list
> Post:   Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
>