I have been developing on the local box up until yesterday when I moved
the dev environment to a common server. Everything works just fine
except for one thing. Rails seems to be caching templates. I cannot
edit a template and make the changes show up without having to bounce
the server (mongrel or webrick, same story).
I checked all the config files for the caching and it is turned off as
far as i can tell. If I put something like raise hell in one of my
controllers, the errors get thrown like usual. Seems like it is just
affecting the templates.
It's not caching urls, just the templates. If I make the controller
return less results or something similar, that shows up fine, but if I
add something to the template, that will not.
If I move the template out of the way between requests, an error gets
thrown, so it is looking for it.
Have not verified if it is persistant or the cache clears after a
while.
It gets stranger. If I make a change to the ruby code in the template,
the page breaks. If I undo my changes, the page is still broken. I'm
it's not strange at all once I figure out what is causing it.
Any ideas? I still can't seem to figure out what's going on and in
order to get our dev environment on a common box where we all use the
same configuration I really need to solve this.
Well, in order to keep my blog up-to-date
Here is what apparently happened, but I don't know why just yet.
The folder the application was sitting in was a mounted nfs share.
I checked out the project into /tmp and fired up a mongrel and there it
was without cache acting just like I wanted it too.
It looks like the cache expires at some point since when I came in this
morning and made a change to a runnning app, it reflected the change,
but when I made a second change it pulled the cached version again.