# Migrations concensus?

**URL:** <https://www.ruby-forum.com/t/migrations-concensus/176995>\
**Category:** Engines\
**Created:** [October 9, 2009, 2:40pm UTC](https://www.ruby-forum.com/t/migrations-concensus/176995 "2009-10-09T14:40:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [October 9, 2009, 2:40pm UTC](https://www.ruby-forum.com/t/migrations-concensus/176995/1 "2009-10-09T14:40:46Z")

</div>

It appears from  
[http://rails-engines.org/news/2009/02/02/engines-in-rails-2-3/](http://rails-engines.org/news/2009/02/02/engines-in-rails-2-3/)

that migrations and copying public assets are no longer supported.

However, from

> <https://github.com/lazyatom/engines/blob/bc5cd970e048dfe5e0e8c06ccf4969bd0d1299be/tasks/engines.rake>

it appears that migrations are still supported via a rake task (for non  
time stamped migrations), and from

[http://groups.google.com/group/rubyonrails-core/browse\_thread/thread/fbc79b21b0ddc3ed/9d6fc87d110061d7?lnk=gst&q=engines#9d6fc87d110061d7](http://groups.google.com/group/rubyonrails-core/browse_thread/thread/fbc79b21b0ddc3ed/9d6fc87d110061d7?lnk=gst&q=engines#9d6fc87d110061d7)

that it still copies in public assets. Anyone have any insights on this  
one?

Was there ever any concensus on these?  
Thanks!  
-r

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [October 12, 2009, 2:50pm UTC](https://www.ruby-forum.com/t/migrations-concensus/176995/2 "2009-10-12T14:50:00Z")

</div>

On 9 Oct 2009, at 13:40, Roger P. wrote:

> It appears from  
> [http://rails-engines.org/news/2009/02/02/engines-in-rails-2-3/](http://rails-engines.org/news/2009/02/02/engines-in-rails-2-3/)
> 
> that migrations and copying public assets are no longer supported.

Of the aspects of ‘engines’ that Rails 2.3 integrated, migrations and  
public asset copying were not included

> that it still copies in public assets. Anyone have any insights on  
> this  
> one?

This is still in the plugin, which can be used along-side Rails 2.3

> Was there ever any concensus on these?  
> Thanks!

Not really. Despite my RailsConf talk essentially being a plea that we  
try and figure this stuff out together, participation really dropped  
off to zero, except for the routing ticket.

- James

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [October 12, 2009, 4:23pm UTC](https://www.ruby-forum.com/t/migrations-concensus/176995/3 "2009-10-12T16:23:41Z")

</div>

> This is still in the plugin, which can be used along-side Rails 2.3

Nice.

> Not really. Despite my RailsConf talk essentially being a plea that we try  
> and figure this stuff out together, participation really dropped off to  
> zero, except for the routing ticket.

I thought that routing was also dropped on the floor–something of a  
“if they want their own order to create routes in, they should tweak  
it all themselves” or something?  
Thanks for engines. Works pretty good.  
-r

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [October 14, 2009, 4:25pm UTC](https://www.ruby-forum.com/t/migrations-concensus/176995/4 "2009-10-14T16:25:14Z")

</div>

On 12 Oct 2009, at 15:22, Roger P. wrote:

> > Not really. Despite my RailsConf talk essentially being a plea that  
> > we try  
> > and figure this stuff out together, participation really dropped  
> > off to  
> > zero, except for the routing ticket.
> 
> I thought that routing was also dropped on the floor–something of a  
> “if they want their own order to create routes in, they should tweak  
> it all themselves” or something?

I believe I had a fairly iron-clad case that plugin routing without  
precidence control was only useful in the simplest of cases, but it’s  
hard to convince a busy entrepreneur of much over IM, and the ‘Russian  
Dolls’ vaporware (no offence, Yehuda) distracted from my own pleas, I  
think.

Only time will tell what the future brings…

All the best,

- James

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [October 12, 2009, 3:04pm UTC](https://www.ruby-forum.com/t/migrations-concensus/176995/5 "2009-10-12T15:04:39Z")

</div>

> Not really. Despite my RailsConf talk essentially being a plea that  
> we try and figure this stuff out together, participation really  
> dropped off to zero, except for the routing ticket.
> 
> - James

I’m sorry I never came to the party with my ideas. I’m still using  
rails 2.1 for production, so it doesn’t affect me, but it might  
eventually ☹

Kind regards,  
Samuel