Re: Time zone issue, Rails 3 - Time.zone = set, but heroku still using local server time

I could be wrong but I believe in Rails 3 the options in Initializers affect the ActiveRecord time (ie. writing to the DB in the local time zone rather than UTC) but Time Zones set in the controllers are supposed to make the application honour time zone settings versus the System Date/Time. I

Re: Time zone issue, Rails 3 - Time.zone = set, but heroku still using local server time

Hi Daryl, I'm still living in 2.3 land, but one thing I often see is using Time.now vs Time.zone.now Also, in test_helper (not sure the rails 3.0 equivalent), I needed to set a default Time.zone - otherwise the Time.zone is nil, so Time.zone.now throws exceptions --Keenan On May 3, 2010, at

Re: Time zone issue, Rails 3 - Time.zone = set, but heroku still using local server time

Hi Daryl, The Time.zone code only affects the behavior of Time.zone (Time.zone.now, Time.zone.parse, ActiveRecord's casting of Date columns, etc) inside your application; it doesn't have any effect on system time (which is what `date` as well as Time.now will give you). The best practice is to