Sean Cribbs wrote:
> The stock environment.rb and boot.rb will load Radiant from
> vendor/radiant automatically.
You mean the stock environment.rb and boot.rb from a Radiant app, right?
Isn't the idea to make RadiantOnRails act like a normal Rails plugin
that can simply be installed from the root of a Rails app with
'script/plugin install radiant_on_rails'?
I believe this is why John laid out the folder structure the way he did:
John W. Long wrote:
>plugins/
> radiant/
> init.rb
> lib/
> vendor/
> radiant/ <<< an svn:external to trunk/radiant
That would be necessary to get auto-loading from a stock Rails app.
There seems to be a little bit of confusion in this thread ("Are we
adding Rails to a Radiant app, or Radiant to a Rails app?"), but I think
this snippet of Loren's original post should clear things up:
Loren Johnson wrote:
> putting Radiant in the vendor directory of an existing
> full-scale Rails app and having it play nicely
I totally agree with Loren that it would be a much more common scenario
to want to retrofit a Rails app with Radiant. I've created more than a
few Rails apps (primarily e-commerce stores) where the site owner
eventually wanted more control over the copy. Update rhtml >> check-in
>> cap deploy gets quite tedious after a while. Retrofitting the app
with Radiant (in an unobtrusive way) would have been a great solution.
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
