Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
I'm not sure if this is an issue with the gem, but I have the gem working live. However, when I used it in a delayed job I get:
Everything is setup just as it would be in production. Running rails 2.3.18 on Ruby 1.8.7
I am considering just storing the rails timezones, how would I do that with the tzinfo gem? If you do it though rails
Doesn't support America/Vancouver, but the tzinfo gem does. Now how would I get the rails timezone from the tzinfo gem so I can replace all of the Linux timezones in my db with the rails ones?
ActiveSupport 2.3 bundles a cut down version of TZInfo. This only includes the time zones defined by
I would suggest checking that the tzinfo gem is installed in the environment where you are running your delayed job and that
ActiveSupport in Rails only defines a limited selection of time zones. It is unlikely that you'd be able to find one for each of the time zones in the IANA Time Zone Database (as used by TZInfo and most Linux distributions). To convert, you'd have to compare the base offsets and daylight savings rules for each of the zones you use with the ActiveSupport definitions.
I think the equivalent ActiveSupport time zone for America/Vancouver is 'Mountain Time (US & Canada)' (which uses America/Denver). This should be correct for conversions since Canada adopted the United States daylight savings rules, but is likely to give incorrect results for conversions before then.