I am using rails 2.3.9, ruby 1.9.3, rubygems 1.8.24, MS SQL Server 2008 R2, and Ubuntu Server 11.04.
Here's my problem:
I am passing an xml file through curl to a web api me and my boss developed, but when the file gets processed, the time appears subtracted by eight hours. My time zone is set at GMT+8, meaning the system is auto-converting my time to UTC. How do i fix this so that my time is set to GMT+8?
Here's the XML file:
<pos-activity>
<siteId>3</siteId>
<transCode>DEP</transCode>
<supervisorCode>1235</supervisorCode>
<amount type="decimal">5000.0</amount>
<data></data>
<date type="datetime">2012-8-16 20:40:04</date>
</pos-activity>
In this example, when this file is processed the resulting time would be 12:40:04 Z
Thank you.
#sometime.in_time_zone("your time zone")
To see a list of time zones, run rake -D time
Change config.time_zone to whatever time zone you want in your environment.rb
Related
I want to use utc+14:00 in my rails app , but
rake time:zones:all
shows up to utc+13:00 only . is there any workaround to use this timezone ?
Rails time zones are a facade around the tzinfo gem, which uses IANA/Olson time zones.
You probably want either the zone "Pacific/Kiritimati", which is in UTC+14 all year, or perhaps "Pacific/Apia", which is in UTC+13 most of the year and in UTC+14 for daylight saving time.
Read the bottom of the timezone tag wiki about Rails time zones, then take a look at the mapping constant. You'll see that "Pacific/Apia" is mapped to the Rails name of "Samoa", but "Pacific/Kiritimati" is not in the map.
The best advice I can offer is to use the TzInfo gem directly, and not use Rails time zone "friendly" names.
How does Rails know my time zone? I don't have it set in application.rb:
# config.time_zone = 'Central Time (US & Canada)'
I searched the whole app for time_zone and that is the only instance of it. I don't see any environment variables for time zone set either. I'm on Windows.
C:\Users\Chloe\workspace\MyBestBody>rails runner "p Time.now"
DL is deprecated, please use Fiddle
2015-06-12 23:38:33 -0400
It prints UTC time when deployed to Heroku.
C:\Users\Chloe\workspace\MyBestBody>heroku run rails console
Running `rails console` attached to terminal... up, run.1949
Loading production environment (Rails 4.2.1)
irb(main):001:0> Time.new
=> 2015-06-13 03:28:34 +0000
Rails 4.2.1
From gettimeofday(), or so the ruby MRI source would have me believe:
int __cdecl
gettimeofday(struct timeval *tv, struct timezone *tz)
{
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
filetime_to_timeval(&ft, tv);
return 0;
}
Per comment, this is a C function, called by the ruby date routines under the hood. You do not call the method yourself, rather you call the ruby methods you are calling.
Your question involves two separate things.
The first is what ruby thinks the time zone is. This is the zone used when you use things likeTime.now or Time.mktime. Ruby uses the C level APIs provided by the operating system to get this information (the TZ environment variable can override this on unixy operating systems).
The second is the time zone your users will see when they use your app. This is frequently not the same thing. Even if your users were all in the same timezone it's a good idea to have your servers use UTC because it is free from things like daylight savings time.
For this reason rails has its own timezone system and the setting you found controls the default value of that timezone. Sometimes you might overwrite this on a per user basis. Rails always records information in UTC, but it will be displayed in views using the value of Time.zone (And input from forms is interpreted in that zone). You can see what the current time in this zone is by doing
Time.zone.now
I have an app that changes behavior based on the time of the day, and I'd like to be able to just spin up the server and test how it works at different times.
Ideally, I'd like to be able to just pass in the time as an argument when I run rails s, like rails s TIME=2014-02-26 22:06:11 -0500.
In config/locales/application.rb you can set the timezone before running rails s.
config.time_zone = 'Alaska'
If you're running OS X, you can also set the system time in the terminal before running rails s.
date 022611002013
The format is [month][day][hh][mm][year], so the above is 11:00 February 26, 2013. You can change your system time back to the current time in the terminal or Date and Time preferences panel.
You can actually read environment variables from within rails (actually Ruby). This is how to do it:
require 'date'
$startup_time = DateTime.parse(ENV['STARTUP_TIME']) rescue DateTime.now
puts "Server started at: #{$startup_time}"
You'd call this code placed in pull_time.rb like this:
STARTUP_TIME="2014-02-26 22:06:11 -0500" ruby pull_time.rb
In order to have this global variable work in Rails, you want to add it to an initializer.
So put the code above in config/initializers/set_startup_time.rb
You can now access $startup_time anywhere in your code. Just pass STARTUP_TIME as an environment variable to rails.
STARTUP_TIME=2014-02-26 22:06:11 -0500 rails s
Rails server uses time of the hosting machine. So if you are running on local machine then changing the time of the local operating system will also have effect on your rails server
If it's hosted on another server then you have to change that server's time.
Don't try changing the time of your server. That can play real havoc with cron jobs or other time-based services.
Instead, have you tried defining the starting time as a specific value in your code then running the server? Then set it to the next time you need, and run the server again?
Time.new(2013, 12, 31, 12, 59, 59) # => 2013-12-31 12:59:59 -0700
You could also use the time as an integer, using the number of seconds that represent the time you want the server to think it is. Pass that in as an ENV hash element, then check to see if it's defined. If it is, define the time based on that value, otherwise don't define the ENV value and the server will run as normal:
ENV['SERVER_TIME'] = '1388519999'
server_time = ENV['SERVER_TIME'] ? Time.at(ENV['SERVER_TIME'].to_i) : Time.now
server_time # => 2013-12-31 12:59:59 -0700
Then, when you need to test the server, you could write a little shell script that sets that value and runs rails s, test the server then quit it, and rerun the shell script with a different value.
You can change Rails' internal timezone by adding config.time_zone = 'Pacific' to application.rb.
If you're deploying to Heroku, you can do the same slightly differently: heroku config:add TZ="Europe/Athens".
However, the downside is that neither of these commands allows you to define a specific time for the app (just the timezone, so you get the current time in another timezone), nor can you run these from command-line when starting your local Rails server.
Rails server determine time from the hosting machine
So changing the system's time would do the trick
EDIT:
As 'sevenseacat' said in comment
you can also use gem timecop to test your application without changing system's time.
The simple thing I want is to store a DateTime in UTC in the database and retrieve it in UTC again, but rails seems to assume I stored the DateTime in my local time zone and adds the 8 hours difference (PST). I have a DateTime field in my model. If I send a request (PUT) to update this field in a particular instance of my model, somehow timezones get mixed up for whatever reason:
Sending to rails via PUT: 2012-02-17T03:46:58Z
Returned via subsequent GET: 2012-02-17T11:46:58Z
The time difference is exactly 8 hours and could be explained by my timezone which is PST (-08:00).
I am using Datamapper 1.2 on Rails 3.1.3.
I set my application config timezone to UTC explicitly.
I also tried to use dm-zone-types. Did not change anything for me.
A git-bisect on my repo revealed, that this misbehavior was introduced as I switched the database to postgres from the original sqlite. This commit only changed the database.yml and the gemfile. Nothing else.
Any ideas?
I have found a hacky solution myself:
Set the servers timezone in the environment variable TZ to 'UTC'. In order to persist this configuration option, I decided to put the environment variable setting in config/boot.rb:
ENV['TZ'] = "UTC"
I still feel dirty and this solution still gives me the willies. So any better/cleaner solution is highly appreciated!
I have some code that seems to execute improperly when it is serialized and run with delayed_job. To get the necessaries out of the way, I am running Ubuntu 11.04, Ruby 1.8.7 with Rails 3.0.4.
I have a datetime field in one of my tables that obviously stores the date and time of a particular event. In my RoR application, I use this field through the application calling strftime on it to format it in different ways. The output of this formatting is correct on the web page.
I am also using delayed_job to put this same field into an email that is sent out (triggered via some action). When the email arrives, it appears that it has somehow been formatted as GMT. For example, if the date time was supposed to be 11-12-2011 15:30:00 (3:30 PM) in the database, the email would read 11-12-2011 22:30:00 (10:30 PM).
I looked in the database and found somethings that are interesting:
The datetime in the database is 2011-11-12 22:30:00
The app, when displayed via the web, formats the data properly as 11-12-2011, 3:30 PM
The email, formats the data properly as 11-12-2011, 10:30 PM
When I run a small ruby file that simply prints the date and time
p Time.now
I get this the correct output (local, non GMT time)
Mon Aug 15 10:15:27 -0600 2011
When I look at what is in the serialized yaml for the delayed_jobs table, I can see that the date field is formatted as
2011-11-12 22:30:00 Z
In my application.rb, I have
config.time_zone = 'Mountain Time (US & Canada)'
and in my environment.rb, I have
timezone = "Mountain Time (US & Canada)"
Can any one help me figure out what is going on here? I am relatively new to RoR, so this may be a super obvious, easy question. If you need any more debug information, please let me know and I can post it up. Similarly, if my question is unclear, I can try to clar
In my case, I solved explicitly specifying the method in_time_zone in the view
example: #my_obj.created_at.in_time_zone.
I know it is not elegant, but so far I have not found better solutions.
Try changing the date object to a string before serializing.
You may want to set the timezone in the database. If it's MySQL, see: http://dev.mysql.com/doc/refman/5.5/en/time-zone-support.html