[Rails] Re: need to restart server every time a controller is generated?

2009-04-22 Thread SpringFlowers AutumnMoon
Philip Hallstrom wrote: >>> You need to restart the server when you add controllers. If you are >>> just changing them then you don't. >> >> oh i just tried Rails 1.2.6 on my macbook. seems like here, we don't >> need to restart server. maybe we only need to restart when it is >> Rails >> 2.0

[Rails] Re: need to restart server every time a controller is generated?

2009-04-22 Thread Philip Hallstrom
>>> but if i don't restart the server, it will say for localhost:3000/ >>> bar >>> >>> Routing Error >>> >>> No route matches "/bar" with {:method=>:get} >>> >>> is it true that we need to restart the server or is there a fast way >>> instead? thanks. >> >> You need to restart the server when yo

[Rails] Re: need to restart server every time a controller is generated?

2009-04-22 Thread SpringFlowers AutumnMoon
Philip Hallstrom wrote: > On Apr 22, 2009, at 7:14 AM, SpringFlowers AutumnMoon wrote: > >> >> but if i don't restart the server, it will say for localhost:3000/bar >> >> Routing Error >> >> No route matches "/bar" with {:method=>:get} >> >> is it true that we need to restart the server or is the

[Rails] Re: need to restart server every time a controller is generated?

2009-04-22 Thread Philip Hallstrom
On Apr 22, 2009, at 7:14 AM, SpringFlowers AutumnMoon wrote: > > i thought we don't need to restart the server by > > ruby script/server > > after we use > > ruby script/generate controller Bar index help > > ? > > but if i don't restart the server, it will say for localhost:3000/bar > > Routi