I'll second that question. I think it would be great to develop specialized versions of Insoshi alongside the main line (in my case, a game portal), but I'm leery of adding migrations for my own specialized data needs. At the moment, I'm sort of taking a "wait until it matures, then freeze and develop from there" approach--which is certainly sub-optimal.
On Jun 14, 12:07 pm, Antony Evans <[EMAIL PROTECTED]> wrote: > Thanks Long, useful to add the rake db:migrate line. > > This brings up a point I've been wondering about for a while: what > happens if we create our own migrations, and then you guys do an > update? Won't this create two migrations with the same version > number, which will mess up the rake command? Or is git smart enough > to remember to change the migration numbers during this process (I > noticed its smart enough to not add config files to the shared > repository so it could be this good!!) > > Antony --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
