rails s -e production
it uses /path/to/tracks/config/environments/production.rb

environment.rb is moved to application.rb in /config, this is a rails3
change. So probably you may need to migrate your custom settings to there

Reinier

> -----Oorspronkelijk bericht-----
> Van: Sebastian Fischmeister [mailto:[email protected]]
> Namens Sebastian Fischmeister
> Verzonden: donderdag 24 mei 2012 23:22
> Aan: Matt Rogers
> CC: Reinier Balt; [email protected]
> Onderwerp: Re: [Tracks-discuss] Re: tracks on rails3
> 
> How do I then start the development mode and which configuration file does
> it use? It seems to use some different configuration file now on my setup.
> 
> Thanks,
>   Sebastian
> 
> On 05/21/12 08:53pm, Matt Rogers wrote:
> > rails server
> >
> > instead of ./script/server
> >
> > Thanks
> > --
> > Matt
> >
> >
> > On Monday, May 21, 2012 at 6:31 PM, Sebastian Fischmeister wrote:
> >
> > > Great job. How do I start the local server in rails 3? The following
> > > doesn't work:
> > >
> > > ./script/server -e development
> > >
> > > Thanks,
> > > Sebastian
> > >
> > > On 05/18/12 08:38pm, Reinier Balt wrote:
> > > > Hi all
> > > >
> > > > I've just merged the rails3 branch. This means that
> > > > * Tracks is migrated to rails 3
> > > > * Tracks runs on ruby 1.9 (tested on 1.9.3)
> > > >
> > > > This migration has some consequences:
> > > > * support for ruby 1.8.7 is going away. You need to have ruby
> > > > 1.9.x for the test environment because some gems depend on it.
> > > > (ruby 1.8.7 will be unsupported from this summer IIRC; Rails 4
> > > > will also work only on ruby 1.9)
> > > > * I hope to maintain tracks 2.2 on 1.8.7, but only if it isn't too
> > > > hard (I'd like to focus my energy on other stuff). N.B. My own
> > > > Tracks server is running ruby 1.8.7, probably until I migrate it
> > > > to Fedora 18 in the end of the year (FC17 will include ruby 1.9)
> > > > * I had to remove support for openid, cas and ldap. I have no
> > > > means to test it (cas, ldap) and the gems we used for openid is
> > > > not supported anymore. I'd like to move to device/omniauth to get
> > > > support back in, preferably in the
> > > > 2.2 timeframe.
> > > > * I had to remove SOAP support, because the gem is not really
> > > > available for rails 3.2 and SOAP is not really believed in anymore
by the
> rails community.
> > > > This means you may need to migrate your scripts (email-to-tracks?)
to
> REST.
> > > > * I you try rails in production environment, do not forget to run
> > > > rake assets:precompile to get all js, css and images working. This
> > > > is not needed for development and test environment.
> > > > * If you have ruby 1.8.7, run
> > > > bundle install --without test
> > > > to avoid installing factory-girl which depends on ruby 1.9
> > > >
> > > > I did get almost all tests running. Those tests not passing have
> > > > issues with the tests, not Tracks functionality :-)
> > > >
> > > > Please help test Tracks on Rails 3.2 out!
> > > >
> > > > Reinier
> > > >
> > > > _______________________________________________
> > > > Tracks-discuss mailing list
> > > > [email protected]
> > > > (mailto:[email protected])
> > > > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
> > >
> > >
> > > _______________________________________________
> > > Tracks-discuss mailing list
> > > [email protected]
> > > (mailto:[email protected])
> > > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
> >
> >
> >

_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

Reply via email to