Hey scott, I'm running into this again What I'm trying to do is avoid 2 database.yml files -- one for my dev machine, one for the deploy server -- by adding a new "staging" environment that is like "test" but on the server Since the server doesnt have a "development" env or db, the rake spec fails Is there a way to force the rake task to copy the schema from "production" rather than "development"?
linoj On Oct 29, 2007, at 10:55 AM, Scott Taylor wrote: > > On Oct 29, 2007, at 9:04 AM, Jonathan Linowes wrote: > >> hi, >> >> When I run rake spec , it seems to be starting with my default >> environment (development or production) and connects to that >> database, before actually connecting to the test one and proceeding >> with the tests. When I remove the development database, the specs >> wont run. How do i initiate rspec to be test environment from the >> start? I dont see this when i run using script/spec > > Well, usually the schema of the development database is copied to the > test one (you wouldn't want to run 100 migrations just because you > fired up your test now, would you?) > > Scott > >> >> linoj >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users > > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
