Rails - Jun 2005 - Rails/lighttpd: Changes to controller not being seen?

This is a weird one:

My app works fine on our local box with webrick. After uploading to TxD 
server, the app starts behaving weirdly. I make some edits to one of 
the controllers and my changes don''t seem to be going through. So I go 
ahead and change the name of the controller file. The page loads 
without error. I figure maybe I''m in the wrong directory, so I change 
the app''s directory name. Great, the app throws a 404. Next step: 
change "app" to "app2". Error. Now I change
"controllers" to
"controllers2". No error! Changing the names of "models" or
"views"
breaks the app, but changing "controllers" doesn''t. After
changing the
directory name (and corresponding name in the config) and restarting 
lighttpd, I manage to break the app by renaming "controllers". WTF?

- Ben
___________________
Ben Jackson
Diretor de Desenvolvimento

ben-p14LI7ZcAE/pVLaUnt/cCQC/G2K4zDHf@public.gmane.org
http://www.incomumdesign.com

Ben Jackson wrote:
> My app works fine on our local box with webrick. After uploading to TxD 
> server, the app starts behaving weirdly. I make some edits to one of the 
> controllers and my changes don''t seem to be going through. So I go
ahead
> and change the name of the controller file. The page loads without 
> error. I figure maybe I''m in the wrong directory, so I change the
app''s
> directory name. Great, the app throws a 404. Next step: change
"app" to
> "app2". Error. Now I change "controllers" to
"controllers2". No error!
> Changing the names of "models" or "views" breaks the
app, but changing
> "controllers" doesn''t. After changing the directory name
(and
> corresponding name in the config) and restarting lighttpd, I manage to 
> break the app by renaming "controllers". WTF?
This is certainly related with you running as ''production''
environment
in the TxD server. In the production environment, code that resides on 
controllers, models and so forth gets all cached in memory, so any 
changes to files does not affect the running application. Only if you 
restart the lighttpd process, you''ll see the changes.

The only code changes visible in the production environment while the 
app is running are changes you make to non-cached view (.rhtml) files.

rgds
Dema
-- 
http://dema.ruby.com.br - Rails development from a .NET perspective

If you are in production mode and you make changes like that you will 
probably need to restart lighttpd for them to take effect. 

Matt Margolis

Ben Jackson wrote:
> This is a weird one:
>
> My app works fine on our local box with webrick. After uploading to 
> TxD server, the app starts behaving weirdly. I make some edits to one 
> of the controllers and my changes don''t seem to be going through.
So I
> go ahead and change the name of the controller file. The page loads 
> without error. I figure maybe I''m in the wrong directory, so I
change
> the app''s directory name. Great, the app throws a 404. Next step: 
> change "app" to "app2". Error. Now I change
"controllers" to
> "controllers2". No error! Changing the names of
"models" or "views"
> breaks the app, but changing "controllers" doesn''t.
After changing the
> directory name (and corresponding name in the config) and restarting 
> lighttpd, I manage to break the app by renaming "controllers".
WTF?
>
> - Ben
> ___________________
> Ben Jackson
> Diretor de Desenvolvimento
>
> ben-p14LI7ZcAE/pVLaUnt/cCQC/G2K4zDHf@public.gmane.org
> http://www.incomumdesign.com
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

I switched to development mode and things seemed to work ok... however  
at some point lighttpd started acting up again and pulling files from  
the cache. At first changing the name of the folder (and the  
corresponding config path) and restarting lighttpd solved the issue,  
however after a little while some bugs from previous versions of the  
app started showing up. Now I have changed the name at least 4 or 5  
times and lighttpd won''t even serve the app:

-bash-2.05b$ lighttpd -D -f lighttpd/lighttpd.conf
Couldn''t write to /home/incomum/sites/id_survey/log/fastcgi.crash.log  
(No such file or directory -  
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
rails/actionpack/lib/action_controller/templates/rescues/ 
routing_error.rhtml [Errno::ENOENT])
[Wed Jun 08 23:13:18 GMT 2005] Dispatcher failed to catch: No such file  
or directory -  
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
rails/actionpack/lib/action_controller/templates/rescues/ 
routing_error.rhtml (Errno::ENOENT)
    
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
rails/actionpack/lib/action_view/base.rb:273:in `read''
    
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
rails/actionpack/lib/action_view/base.rb:273:in `read_template_file''

The path /home/incomum/sites/id_survey/log/fastcgi.crash.log is from an  
old version of dispatch.fcgi that specified the RAILS_ROOT path  
absolutely. I changed the path to RAILS_ROOT = File.dirname(__FILE__) +  
"/../", however this error is still showing up in lighttpd''s
error log.
id_survey_deploy_new is one of the older names of the directory from  
when I was changing it.

I have turned off mod_compress to no avail. My head hurts :(

Thanks,
Ben

On Jun 7, 2005, at 11:58 PM, Demetrius Nunes wrote:
> Ben Jackson wrote:
>> My app works fine on our local box with webrick. After uploading to  
>> TxD server, the app starts behaving weirdly. I make some edits to one  
>> of the controllers and my changes don''t seem to be going
through. So
>> I go ahead and change the name of the controller file. The page loads  
>> without error. I figure maybe I''m in the wrong directory, so I
change
>> the app''s directory name. Great, the app throws a 404. Next
step:
>> change "app" to "app2". Error. Now I change
"controllers" to
>> "controllers2". No error! Changing the names of
"models" or "views"
>> breaks the app, but changing "controllers" doesn''t.
After changing
>> the directory name (and corresponding name in the config) and  
>> restarting lighttpd, I manage to break the app by renaming  
>> "controllers". WTF?
>
> This is certainly related with you running as
''production'' environment
> in the TxD server. In the production environment, code that resides on  
> controllers, models and so forth gets all cached in memory, so any  
> changes to files does not affect the running application. Only if you  
> restart the lighttpd process, you''ll see the changes.
>
> The only code changes visible in the production environment while the  
> app is running are changes you make to non-cached view (.rhtml) files.
>
> rgds
> Dema
> -- 
> http://dema.ruby.com.br - Rails development from a .NET perspective
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

Update: after waiting half an hour and restarting lighttpd it seems to  
be working ok.
*crosses fingers*

- Ben

On Jun 8, 2005, at 8:26 PM, Ben Jackson wrote:
> I switched to development mode and things seemed to work ok... however  
> at some point lighttpd started acting up again and pulling files from  
> the cache. At first changing the name of the folder (and the  
> corresponding config path) and restarting lighttpd solved the issue,  
> however after a little while some bugs from previous versions of the  
> app started showing up. Now I have changed the name at least 4 or 5  
> times and lighttpd won''t even serve the app:
>
> -bash-2.05b$ lighttpd -D -f lighttpd/lighttpd.conf
> Couldn''t write to
/home/incomum/sites/id_survey/log/fastcgi.crash.log
> (No such file or directory -  
> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
> rails/actionpack/lib/action_controller/templates/rescues/ 
> routing_error.rhtml [Errno::ENOENT])
> [Wed Jun 08 23:13:18 GMT 2005] Dispatcher failed to catch: No such  
> file or directory -  
> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
> rails/actionpack/lib/action_controller/templates/rescues/ 
> routing_error.rhtml (Errno::ENOENT)
>    
> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
> rails/actionpack/lib/action_view/base.rb:273:in `read''
>    
> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
> rails/actionpack/lib/action_view/base.rb:273:in
`read_template_file''
>
> The path /home/incomum/sites/id_survey/log/fastcgi.crash.log is from  
> an old version of dispatch.fcgi that specified the RAILS_ROOT path  
> absolutely. I changed the path to RAILS_ROOT = File.dirname(__FILE__)  
> + "/../", however this error is still showing up in
lighttpd''s error
> log. id_survey_deploy_new is one of the older names of the directory  
> from when I was changing it.
>
> I have turned off mod_compress to no avail. My head hurts :(
>
> Thanks,
> Ben
>
> On Jun 7, 2005, at 11:58 PM, Demetrius Nunes wrote:
>
>> Ben Jackson wrote:
>>> My app works fine on our local box with webrick. After uploading to
>>> TxD server, the app starts behaving weirdly. I make some edits to  
>>> one of the controllers and my changes don''t seem to be
going
>>> through. So I go ahead and change the name of the controller file.
>>> The page loads without error. I figure maybe I''m in the
wrong
>>> directory, so I change the app''s directory name. Great,
the app
>>> throws a 404. Next step: change "app" to
"app2". Error. Now I change
>>> "controllers" to "controllers2". No error!
Changing the names of
>>> "models" or "views" breaks the app, but
changing "controllers"
>>> doesn''t. After changing the directory name (and
corresponding name
>>> in the config) and restarting lighttpd, I manage to break the app
by
>>> renaming "controllers". WTF?
>>
>> This is certainly related with you running as
''production''
>> environment in the TxD server. In the production environment, code  
>> that resides on controllers, models and so forth gets all cached in  
>> memory, so any changes to files does not affect the running  
>> application. Only if you restart the lighttpd process, you''ll
see the
>> changes.
>>
>> The only code changes visible in the production environment while the  
>> app is running are changes you make to non-cached view (.rhtml)  
>> files.
>>
>> rgds
>> Dema
>> -- 
>> http://dema.ruby.com.br - Rails development from a .NET perspective
>>
>> _______________________________________________
>> Rails mailing list
>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>> http://lists.rubyonrails.org/mailman/listinfo/rails

Update: Just checked today and the old bugs are resurfacing. I have  
changed nothing in the config. Does anyone have any idea what might be  
causing this? Thanks,

Ben

*Pulls hair in frustration*

On Jun 8, 2005, at 8:54 PM, Ben Jackson wrote:
> Update: after waiting half an hour and restarting lighttpd it seems to  
> be working ok.
> *crosses fingers*
>
> - Ben
>
> On Jun 8, 2005, at 8:26 PM, Ben Jackson wrote:
>
>> I switched to development mode and things seemed to work ok...  
>> however at some point lighttpd started acting up again and pulling  
>> files from the cache. At first changing the name of the folder (and  
>> the corresponding config path) and restarting lighttpd solved the  
>> issue, however after a little while some bugs from previous versions  
>> of the app started showing up. Now I have changed the name at least 4  
>> or 5 times and lighttpd won''t even serve the app:
>>
>> -bash-2.05b$ lighttpd -D -f lighttpd/lighttpd.conf
>> Couldn''t write to
/home/incomum/sites/id_survey/log/fastcgi.crash.log
>> (No such file or directory -  
>> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
>> rails/actionpack/lib/action_controller/templates/rescues/ 
>> routing_error.rhtml [Errno::ENOENT])
>> [Wed Jun 08 23:13:18 GMT 2005] Dispatcher failed to catch: No such  
>> file or directory -  
>> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
>> rails/actionpack/lib/action_controller/templates/rescues/ 
>> routing_error.rhtml (Errno::ENOENT)
>>    
>> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
>> rails/actionpack/lib/action_view/base.rb:273:in `read''
>>    
>> /home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/ 
>> rails/actionpack/lib/action_view/base.rb:273:in
`read_template_file''
>>
>> The path /home/incomum/sites/id_survey/log/fastcgi.crash.log is from  
>> an old version of dispatch.fcgi that specified the RAILS_ROOT path  
>> absolutely. I changed the path to RAILS_ROOT = File.dirname(__FILE__)  
>> + "/../", however this error is still showing up in
lighttpd''s error
>> log. id_survey_deploy_new is one of the older names of the directory  
>> from when I was changing it.
>>
>> I have turned off mod_compress to no avail. My head hurts :(
>>
>> Thanks,
>> Ben
>>
>> On Jun 7, 2005, at 11:58 PM, Demetrius Nunes wrote:
>>
>>> Ben Jackson wrote:
>>>> My app works fine on our local box with webrick. After
uploading to
>>>> TxD server, the app starts behaving weirdly. I make some edits
to
>>>> one of the controllers and my changes don''t seem to be
going
>>>> through. So I go ahead and change the name of the controller
file.
>>>> The page loads without error. I figure maybe I''m in
the wrong
>>>> directory, so I change the app''s directory name.
Great, the app
>>>> throws a 404. Next step: change "app" to
"app2". Error. Now I
>>>> change "controllers" to "controllers2". No
error! Changing the
>>>> names of "models" or "views" breaks the
app, but changing
>>>> "controllers" doesn''t. After changing the
directory name (and
>>>> corresponding name in the config) and restarting lighttpd, I
manage
>>>> to break the app by renaming "controllers". WTF?
>>>
>>> This is certainly related with you running as
''production''
>>> environment in the TxD server. In the production environment, code
>>> that resides on controllers, models and so forth gets all cached in
>>> memory, so any changes to files does not affect the running  
>>> application. Only if you restart the lighttpd process,
you''ll see
>>> the changes.
>>>
>>> The only code changes visible in the production environment while  
>>> the app is running are changes you make to non-cached view (.rhtml)
>>> files.
>>>
>>> rgds
>>> Dema
>>> -- 
>>> http://dema.ruby.com.br - Rails development from a .NET perspective
>>>
>>> _______________________________________________
>>> Rails mailing list
>>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

Why don''t you develop on localhost, make sure your app works and rsync
it to production when everything is alright. Remote dev always ends up
in a mess like this.

Some of the problems you are seeing could be results of syntax errors
in the ruby files. Try to integrate ruby -c <current file> into your
Editor on a hotkey. That will check the syntax of the file.

On 6/9/05, Ben Jackson
<ben-p14LI7ZcAE/pVLaUnt/cCQC/G2K4zDHf@public.gmane.org>
wrote:
> Update: Just checked today and the old bugs are resurfacing. I have
> changed nothing in the config. Does anyone have any idea what might be
> causing this? Thanks,
> 
> Ben
> 
> *Pulls hair in frustration*
> 
> On Jun 8, 2005, at 8:54 PM, Ben Jackson wrote:
> 
> > Update: after waiting half an hour and restarting lighttpd it seems to
> > be working ok.
> > *crosses fingers*
> >
> > - Ben
> >
> > On Jun 8, 2005, at 8:26 PM, Ben Jackson wrote:
> >
> >> I switched to development mode and things seemed to work ok...
> >> however at some point lighttpd started acting up again and pulling
> >> files from the cache. At first changing the name of the folder
(and
> >> the corresponding config path) and restarting lighttpd solved the
> >> issue, however after a little while some bugs from previous
versions
> >> of the app started showing up. Now I have changed the name at
least 4
> >> or 5 times and lighttpd won''t even serve the app:
> >>
> >> -bash-2.05b$ lighttpd -D -f lighttpd/lighttpd.conf
> >> Couldn''t write to
/home/incomum/sites/id_survey/log/fastcgi.crash.log
> >> (No such file or directory -
> >>
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/
> >> rails/actionpack/lib/action_controller/templates/rescues/
> >> routing_error.rhtml [Errno::ENOENT])
> >> [Wed Jun 08 23:13:18 GMT 2005] Dispatcher failed to catch: No such
> >> file or directory -
> >>
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/
> >> rails/actionpack/lib/action_controller/templates/rescues/
> >> routing_error.rhtml (Errno::ENOENT)
> >>
> >>
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/
> >> rails/actionpack/lib/action_view/base.rb:273:in `read''
> >>
> >>
/home/incomum/sites/id_survey_deploy_new/public/../config/..//vendor/
> >> rails/actionpack/lib/action_view/base.rb:273:in
`read_template_file''
> >>
> >> The path /home/incomum/sites/id_survey/log/fastcgi.crash.log is
from
> >> an old version of dispatch.fcgi that specified the RAILS_ROOT path
> >> absolutely. I changed the path to RAILS_ROOT =
File.dirname(__FILE__)
> >> + "/../", however this error is still showing up in
lighttpd''s error
> >> log. id_survey_deploy_new is one of the older names of the
directory
> >> from when I was changing it.
> >>
> >> I have turned off mod_compress to no avail. My head hurts :(
> >>
> >> Thanks,
> >> Ben
> >>
> >> On Jun 7, 2005, at 11:58 PM, Demetrius Nunes wrote:
> >>
> >>> Ben Jackson wrote:
> >>>> My app works fine on our local box with webrick. After
uploading to
> >>>> TxD server, the app starts behaving weirdly. I make some
edits to
> >>>> one of the controllers and my changes don''t seem
to be going
> >>>> through. So I go ahead and change the name of the
controller file.
> >>>> The page loads without error. I figure maybe I''m
in the wrong
> >>>> directory, so I change the app''s directory name.
Great, the app
> >>>> throws a 404. Next step: change "app" to
"app2". Error. Now I
> >>>> change "controllers" to
"controllers2". No error! Changing the
> >>>> names of "models" or "views" breaks
the app, but changing
> >>>> "controllers" doesn''t. After changing
the directory name (and
> >>>> corresponding name in the config) and restarting lighttpd,
I manage
> >>>> to break the app by renaming "controllers". WTF?
> >>>
> >>> This is certainly related with you running as
''production''
> >>> environment in the TxD server. In the production environment,
code
> >>> that resides on controllers, models and so forth gets all
cached in
> >>> memory, so any changes to files does not affect the running
> >>> application. Only if you restart the lighttpd process,
you''ll see
> >>> the changes.
> >>>
> >>> The only code changes visible in the production environment
while
> >>> the app is running are changes you make to non-cached view
(.rhtml)
> >>> files.
> >>>
> >>> rgds
> >>> Dema
> >>> --
> >>> http://dema.ruby.com.br - Rails development from a .NET
perspective
> >>>
> >>> _______________________________________________
> >>> Rails mailing list
> >>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> >>> http://lists.rubyonrails.org/mailman/listinfo/rails
> >
> > _______________________________________________
> > Rails mailing list
> > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
> >
> 
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 

-- 
Tobi
http://www.snowdevil.ca - Snowboards that don''t suck
http://typo.leetsoft.com - Open source weblog engine
http://blog.leetsoft.com - Technical weblog

We are developing on localhost. We put a production version on the  
server, found some error messages that hadn''t been localized, and upped
a new version via ftp, at which point we started wondering why the app  
wasn''t reflecting our changes. Also we were on dialup at the time (just
moved), so editing on the server was an unfortunate necessity :)

I have syntax-checked the entire app and found no problems. I have also  
passed this thread to the lighttpd list. Thanks,
Ben

On Jun 9, 2005, at 6:31 PM, Tobias Luetke wrote:
> Why don''t you develop on localhost, make sure your app works and
rsync
> it to production when everything is alright. Remote dev always ends up
> in a mess like this.
>
> Some of the problems you are seeing could be results of syntax errors
> in the ruby files. Try to integrate ruby -c <current file> into your
> Editor on a hotkey. That will check the syntax of the file.
>
> On 6/9/05, Ben Jackson
<ben-p14LI7ZcAE/pVLaUnt/cCQC/G2K4zDHf@public.gmane.org> wrote:
>> Update: Just checked today and the old bugs are resurfacing. I have
>> changed nothing in the config. Does anyone have any idea what might be
>> causing this? Thanks,
>>
>> Ben
>>
>> *Pulls hair in frustration*
>>
>> On Jun 8, 2005, at 8:54 PM, Ben Jackson wrote:
>>
>>> Update: after waiting half an hour and restarting lighttpd it seems
>>> to
>>> be working ok.
>>> *crosses fingers*
>>>
>>> - Ben
>>>
>>> On Jun 8, 2005, at 8:26 PM, Ben Jackson wrote:
>>>
>>>> I switched to development mode and things seemed to work ok...
>>>> however at some point lighttpd started acting up again and
pulling
>>>> files from the cache. At first changing the name of the folder
(and
>>>> the corresponding config path) and restarting lighttpd solved
the
>>>> issue, however after a little while some bugs from previous
versions
>>>> of the app started showing up. Now I have changed the name at
least
>>>> 4
>>>> or 5 times and lighttpd won''t even serve the app:
>>>>
>>>> -bash-2.05b$ lighttpd -D -f lighttpd/lighttpd.conf
>>>> Couldn''t write to  
>>>> /home/incomum/sites/id_survey/log/fastcgi.crash.log
>>>> (No such file or directory -
>>>> /home/incomum/sites/id_survey_deploy_new/public/../config/..// 
>>>> vendor/
>>>> rails/actionpack/lib/action_controller/templates/rescues/
>>>> routing_error.rhtml [Errno::ENOENT])
>>>> [Wed Jun 08 23:13:18 GMT 2005] Dispatcher failed to catch: No
such
>>>> file or directory -
>>>> /home/incomum/sites/id_survey_deploy_new/public/../config/..// 
>>>> vendor/
>>>> rails/actionpack/lib/action_controller/templates/rescues/
>>>> routing_error.rhtml (Errno::ENOENT)
>>>>
>>>> /home/incomum/sites/id_survey_deploy_new/public/../config/..// 
>>>> vendor/
>>>> rails/actionpack/lib/action_view/base.rb:273:in `read''
>>>>
>>>> /home/incomum/sites/id_survey_deploy_new/public/../config/..// 
>>>> vendor/
>>>> rails/actionpack/lib/action_view/base.rb:273:in
`read_template_file''
>>>>
>>>> The path /home/incomum/sites/id_survey/log/fastcgi.crash.log is
from
>>>> an old version of dispatch.fcgi that specified the RAILS_ROOT
path
>>>> absolutely. I changed the path to RAILS_ROOT =  
>>>> File.dirname(__FILE__)
>>>> + "/../", however this error is still showing up in
lighttpd''s error
>>>> log. id_survey_deploy_new is one of the older names of the
directory
>>>> from when I was changing it.
>>>>
>>>> I have turned off mod_compress to no avail. My head hurts :(
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>> On Jun 7, 2005, at 11:58 PM, Demetrius Nunes wrote:
>>>>
>>>>> Ben Jackson wrote:
>>>>>> My app works fine on our local box with webrick. After
uploading
>>>>>> to
>>>>>> TxD server, the app starts behaving weirdly. I make
some edits to
>>>>>> one of the controllers and my changes don''t
seem to be going
>>>>>> through. So I go ahead and change the name of the
controller file.
>>>>>> The page loads without error. I figure maybe
I''m in the wrong
>>>>>> directory, so I change the app''s directory
name. Great, the app
>>>>>> throws a 404. Next step: change "app" to
"app2". Error. Now I
>>>>>> change "controllers" to
"controllers2". No error! Changing the
>>>>>> names of "models" or "views" breaks
the app, but changing
>>>>>> "controllers" doesn''t. After
changing the directory name (and
>>>>>> corresponding name in the config) and restarting
lighttpd, I
>>>>>> manage
>>>>>> to break the app by renaming "controllers".
WTF?
>>>>>
>>>>> This is certainly related with you running as
''production''
>>>>> environment in the TxD server. In the production
environment, code
>>>>> that resides on controllers, models and so forth gets all
cached in
>>>>> memory, so any changes to files does not affect the running
>>>>> application. Only if you restart the lighttpd process,
you''ll see
>>>>> the changes.
>>>>>
>>>>> The only code changes visible in the production environment
while
>>>>> the app is running are changes you make to non-cached view
(.rhtml)
>>>>> files.
>>>>>
>>>>> rgds
>>>>> Dema
>>>>> --
>>>>> http://dema.ruby.com.br - Rails development from a .NET
perspective
>>>>>
>>>>> _______________________________________________
>>>>> Rails mailing list
>>>>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>>
>>> _______________________________________________
>>> Rails mailing list
>>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>>
>>
>> _______________________________________________
>> Rails mailing list
>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>
>
>
> -- 
> Tobi
> http://www.snowdevil.ca - Snowboards that don''t suck
> http://typo.leetsoft.com - Open source weblog engine
> http://blog.leetsoft.com - Technical weblog
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>