Hi Tim,
Yep, the migration seemed to work. The error is a result of the a
route resolving to the TodoController, which shouldn't happen in the
trunk as it's been renamed TodosController (note the plural). Can you
confirm that this is the same instance of Tracks that was
successfully running starting with blank DB? If so, go ahead and
attach your config/routes.rb file so I can do a sanity check for myself.
Cheers from NYC,
Luke
On Nov 8, 2007, at 11:39 AM, Tim Madden wrote:
OK- The rake db:migrate RAILS_ENV=production seemed to work, but
the application errored out. I have attached the output of the rake
command and the production.log if that helps...
Tim
On Thu, 2007-11-08 at 07:46 -0500, Luke Melia wrote:
We haven't specifically addressed the upgrade scenario yet (though
this is clearly important for the 1.5 release). That said, you could
help us test it out!
* Make a copy of your database.
* Configure the trunk version's database.yml to point at it as the
production database .
* From the directory where you have the trunk run "rake db:migrate
RAILS_ENV=production"
* Send us your output.
* Start up Tracks in production mode.
It might just work. If not, we can make changes to support it.
On Nov 8, 2007, at 7:37 AM, Tim Madden wrote:
> So I am new the tracks trunk and I have a question. I have been
> able to get it going with a blank database, but would like use my
> own tracks data in the new trunk database. I am using MySQL on
> linux. Is there a guide or quick way to do it?
>
> Thanks,
> Tim
> _______________________________________________
> Tracks-discuss mailing list
> [email protected]
> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
<server error message.txt>
<production.log>
<rake output.txt>
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
