UPDATE: Ok, I didn't formulate a good Q to be answered. I still struggle with heroku being on -07:00 UTC and I at +02:200 UTC.
Q: How do I get the log written in the correct Time.
zone ?
The 9 hours difference, heroku (us west) - norway, is distracting to work with. I get this in my production.log (using heroku logs):
Processing ProductionController#create to xml (for 81.26.51.35 at 2010-04-28 23:00:12) [POST]
How do I get it to write 2010-04-29 08:00:12 +02:00 GMT ?
Note that I'm running at heroku and cannot set the server time myself, as one could do at your amazon EC2 servers. Below is my previous question, I'll leave it be as it holds some interesting information about time and zones.
Why does Time.now yield the server local time when I have set the another time
zone in my environment.rb
config.time_zone = 'Copenhagen'
I've put this in a view
<p> Time.
zone <%= Time.
zone %> </p>
<p> Time.now <%= Time.now %> </p>
<p> Time.now.utc <%= Time.now.utc %> </p>
<p> Time.
zone.now <%= Time.
zone.now %> </p>
<p> Time.
zone.today <%= Time.
zone.today %> </p>
rendering this result on my app at heroku
Time.
zone (GMT+01:00) Copenhagen
Time.now Mon Apr 26 08:28:21 -0700
2010
Time.now.utc Mon Apr 26 15:28:21 UTC
2010
Time.
zone.now 2010-04-26 17:28:21
+0200
Time.
zone.today 2010-04-26
Time.
zone.now yields the correct result. Do I have to switch from Time.now to Time.
zone.now, everywhere? Seems cumbersome. I truly don't care what the local time of the server is, it's giving me loads of trouble due to extensive use of Time.now. Am I misunderstanding anything fundamental here?
