rubyonrailsin

I've also toyed with the idea of rsync to move everything over to
where it needs to be on startup. This means you have duplicate copies
of everything (migrations, images, stylesheets, etc.) but it would
significantly improve performance. We have noticed a big time slow
down with all rake tasks because we're scanning the entire extension
tree. Having this type of sync would also make stuff way more Heroku
friendly.

Thoughts?

On Tue, Mar 30, 2010 at 11:57 PM, Sean Cribbs <seancribbs@gmail.com> wrote:
> In the current implementation, we hack things to get migrations living
> in different places, and furthermore, we prefix each migration in the
> schema_migrations table with the extension name.  One of those patches
> looked like it indicated the engine from which the migration
> originated, but in general a generator makes most sense.
>
> On Tue, Mar 30, 2010 at 8:14 PM, Travis D Warlick Jr
> <warlickt@operissystems.com> wrote:
>> Good discussion on the whole plugin migrations problem:
>> https://rails.lighthouseapp.com/projects/8994/tickets/2058
>>
>> Having read through that, I agree that each extension should generate its
>> own migrations, at least until the Rails core team implements a common
>> solution.
>>
>> -- Travis Warlick
>>
>> On 3/30/10 6:53 PM, John Long wrote:
>>>
>>> On migrations, I'm wondering if we should take a different approach.
>>> Perhaps each extension should just generate the necessary migrations?
>>>
>>> --
>>> John Long
>>> http://wiseheartdesign.com
>>> http://recursivecreative.com
>>>
>>> On Tue, Mar 30, 2010 at 3:05 PM, Sean Schofield
>>> <sean.schofield@gmail.com>  wrote:
>>>>
>>>> I have several thoughts on how to approach this but the client work is
>>>> getting insane again.  I'll take a rough stab at this sometime soon
>>>> and report back what I find.  Basically I think we can use Rails3 for
>>>> most everything.  We just need to understand more about the
>>>> limitations or gotchas that require additional spree/radiant hacks.
>>>> With any luck its nothing and this is just an exercise in proving
>>>> that.
>>>>
>>>> Sean Schofield
>>>>
>>>> On Mon, Mar 29, 2010 at 1:31 PM, Travis D Warlick Jr
>>>> <warlickt@operissystems.com>  wrote:
>>>>>
>>>>> I think this is a wonderful idea.  In my walk-throughs of new Rails 3
>>>>> code,
>>>>> I've noticed a number of things that Rails now has .  Count me in for
>>>>> help.
>>>>>
>>>>> I'd like to throw out an idea (which may require a new thread, but I'll
>>>>> start it here since it's closely related): Radiant/spree as a plugin
>>>>> gem.  I
>>>>> have a very large upcoming project.  It needs a CMS, but it also needs
>>>>> functionality that Radiant isn't the best choice for.  Currently, I'm
>>>>> forced
>>>>> to write two apps, which doesn't sit well with me.
>>>>>
>>>>> Here's my hypotheses on the benefits of using a plugin gem:
>>>>>
>>>>> * Passenger memory savings with smart spawning.
>>>>> * Built-in support for extension dependencies.
>>>>> * radiant command offload to rails -m<radiant-install-script>
>>>>>  - easy integration of "radiant-more" via install scripts?
>>>>>  - radiant-more install script repository, similiar to
>>>>> ext.radiantcms.org?
>>>>>
>>>>> Thoughts? Criticisms?
>>>>>
>>>>> -- Travis Warlick
>>>>>
>>>>> On 3/26/10 7:48 PM, Sean Schofield wrote:
>>>>>>
>>>>>> I'd like to introduce myself.  My name is Sean Schofield, and I'm the
>>>>>> creator of the Spree e-commerce project.  Spree has an extension
>>>>>> system very similar to the one in Radiant.  Actually we based our
>>>>>> extension system on the one in Radiant and received some very helpful
>>>>>> insight from Sean Cribbs at the time.
>>>>>>
>>>>>> Now that Rails3 is rolling around we're finding ourselves discussing
>>>>>> the future of extensions.  We're planning on taking a serious look at
>>>>>> this issue starting a few weeks from now.  One of the guys on the
>>>>>> Spree core team suggested that we might want to reach out to the
>>>>>> Radiant devs to see if they were interested in working together on
>>>>>> this problem.  A side benefit would be that it could become easier to
>>>>>> integrate Spree and Radiant for sites that require both e-commerce and
>>>>>> CMS.
>>>>>>
>>>>>> So I wanted to ask if there was any interest in working on a common
>>>>>> solution for implementing Radiant/Spree style extensions in Rails3.  I
>>>>>> was thinking we might want to create a separate github project for the
>>>>>> purposes of exploring this.  It could serve as a starting point for
>>>>>> exploring the concept but maybe it could evolve into a stand-alone gem
>>>>>> dependency that would work with Radiant or Spree.
>>>>>>
>>>>>> Is there any interest in exploring this together from the Radiant
>>>>>> community?
>>>>>>
>>>>>> Sean
>>>>>>
>>>>>
>>>>> --
>>>>> Radiant CMS Dev Mailing List
>>>>> Post:        radiantcms-dev@googlegroups.com
>>>>> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
>>>>> Group Site:  http://groups.google.com/group/radiantcms-dev/
>>>>>
>>>>> To unsubscribe from this group, send email to
>>>>> radiantcms-dev+unsubscribegooglegroups.com or reply to this email with
>>>>> the
>>>>> words "REMOVE ME" as the subject.
>>>>>
>>>>
>>>> --
>>>> Radiant CMS Dev Mailing List
>>>> Post:        radiantcms-dev@googlegroups.com
>>>> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
>>>> Group Site:  http://groups.google.com/group/radiantcms-dev/
>>>>
>>>> To unsubscribe from this group, send email to
>>>> radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the
>>>> words "REMOVE ME" as the subject.
>>>>
>>>
>>
>> --
>> Radiant CMS Dev Mailing List
>> Post:        radiantcms-dev@googlegroups.com
>> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
>> Group Site:  http://groups.google.com/group/radiantcms-dev/
>
> --
> Radiant CMS Dev Mailing List
> Post:        radiantcms-dev@googlegroups.com
> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
> Group Site:  http://groups.google.com/group/radiantcms-dev/

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/