Re: db:pull - timezones

One thing I have done successfully is to set ENV[TZ] = UTC early in my config/environment.rb. That ensure the full Rails process is always in UTC. Time.now will now be the same as Time.now.utc. Hope that helps! François Beausoleil http://blog.teksol.info/

root CNAME with slicehost DNS

Hey there - I'm having problems getting a root level CNAME to register on heroku. Since I've got other root domains CNAME'd to github, I'm fairly certain that it can work for heroku as well. Here's what I've tried so far: 1. set up slicehost dns, CNAME both www subdomain and root domain to

heroku gem v0.7

Hi, The v0.7 gem errors when installed, with the following message: custom_require.rb:31:in `gem_original_require': no such file to load -- json (LoadError) I believe that you need to add a dependency in the gem, to install the json gem. Once installed, v0.7 worked fine. Thanks.

Re: root CNAME with slicehost DNS

One reason this can happen is that the DNS info was cached on the local nameserver prior to it propagating from your provider (Slicehost, in this case). In that case you have to wait about 20 minutes for the cache to clear. Can you try it again right now and let me know if it works? We've got

Re: internal server error when trying to add a custom domain

Finally worked. [dali:~/yurified git:master] heroku domains:add www.yurified.com Internal server error [dali:~/yurified git:master] heroku domains:add www.yurified.com Internal server error [dali:~/yurified git:master] heroku domains:add www.yurified.com Internal server error [dali:~/yurified

Re: root CNAME with slicehost DNS

three hours after your message, i was able to try it and am up and running. thanks! On Apr 8, 4:12 pm, Adam Wiggins a...@heroku.com wrote: One reason this can happen is that the DNS info was cached on the local nameserver prior to it propagating from your provider (Slicehost, in this case).