Keep it simple, use UTC - all the time. Only convert and display in timezones when you need. I wish all my data sources were UTC....
That said if your only working in one timezone it probably doesn't matter and choose whatever you like. If your in EST and you don't have to do conversion EST is fine. Only my 2 cents though. -Jon On Sep 1, 10:38 am, "Mike P." <[email protected]> wrote: > Hello, > > I keep seeing conflicting recommendations on dealing with time zones > on Heroku, and I'm really not sure what to do. For example: > > 1) This post (which I think may be from someone at Heroku) says to use > UTC: > > -http://groups.google.com/group/heroku/browse_thread/thread/8e7566a7b8... > > 2) This post gives a suggestion to specify the Heroku time zone in the > application: > > -http://stackoverflow.com/questions/2719330/heroku-time-zone-problem-l... > > 3) This post recommends specifying a TimeZone during a heroku db:pull > call > > -http://stackoverflow.com/questions/1416294/weird-time-inconsistencies... > > And so on... > > I'm inclined to go with number 1, but does anyone have any suggestions/ > recommendations/tips or "best practices" on dealing with this time > zone issue? > > Right now, my time zone is set to "Eastern Time (US & Canada)" in > environment.rb, and the date/time columns in my Postgre tables are set > to "timestamp without time zone." The users will have their own > timezone setting that will be used throughout the app. > > Is there anything else I should be doing? How can I eliminate any > potential timing issues between development and running on Heroku in > production? Any thoughts or advice would be greatly appreciated. > > Thank you very much, > Mike -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
