<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Heroku - Latest Comments</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#forumcomments-b571ecea" type="application/json"/><link>http://heroku.disqus.com/</link><description></description><language>en</language><lastBuildDate>Mon, 16 Nov 2009 14:18:56 -0000</lastBuildDate><item><title>Re: Heroku | Radiant CMS in 5 Minutes Or Less</title><link>http://blog.heroku.com/archives/2009/3/26/radiant_cms_in_5_minutes_or_less/#comment-23216187</link><description>Any chance you might be able to add the versions of radiant/rails/heroku gems to which this tutorial applies?  Without a year at the end of the blog post date, I'm not quite sure if I'm not doing something according to spec, or if these directions are just a little out-of-date.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">soychicka</dc:creator><pubDate>Mon, 16 Nov 2009 14:18:56 -0000</pubDate></item><item><title>Re: Heroku | Interested in talking with Heroku at Rubyconf?</title><link>http://blog.heroku.com/archives/2009/11/12/interested_in_talking_with_heroku_at_rubyconf/#comment-22881452</link><description>Wow sushi, nice! step up from the typically Pizza and soda/beer in my opinion. I think it is cheaper in SF than the Midwest though, and definitely fresher. :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">webandy</dc:creator><pubDate>Fri, 13 Nov 2009 01:05:49 -0000</pubDate></item><item><title>Re: Heroku | Tech: Sending email with Gmail</title><link>http://blog.heroku.com/archives/2009/11/9/tech_sending_email_with_gmail/#comment-22872192</link><description>Your instructions are wrong...&lt;br&gt;It should be: heroku config:add &lt;a href="mailto:GMAIL_SMTP_USER=username@gmail.com" rel="nofollow"&gt;GMAIL_SMTP_USER=username@gmail.com&lt;/a&gt;&lt;br&gt;Instead of: heroku config &lt;a href="mailto:GMAIL_SMTP_USER=username@gmail.com" rel="nofollow"&gt;GMAIL_SMTP_USER=username@gmail.com&lt;/a&gt;&lt;br&gt;Same for the pass...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jordinl</dc:creator><pubDate>Thu, 12 Nov 2009 21:34:44 -0000</pubDate></item><item><title>Re: Heroku | Add-ons Launch</title><link>http://blog.heroku.com/archives/2009/10/29/add_ons_launch/#comment-22865819</link><description>From &lt;a href="http://heroku.com/myapss" rel="nofollow"&gt;http://heroku.com/myapss&lt;/a&gt;, you can select your app, select the add-on in the upper right corner add-ons menu, then remove with the button at the bottom of the page.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">teich</dc:creator><pubDate>Thu, 12 Nov 2009 18:53:44 -0000</pubDate></item><item><title>Re: Heroku | Howto: Heroku + Hoptoad</title><link>http://blog.heroku.com/archives/2008/9/17/23_howto_heroku_hoptoad/#comment-22788286</link><description>Hello&lt;br&gt;&lt;br&gt;There seems to be a conflict in Rails 2.3.3 and the current version of the Hoptoad Notifier... resulting in a 500 Server error:&lt;br&gt;&lt;br&gt;  Status: 500 Internal Server Error&lt;br&gt;  undefined method `to_hash' for #&amp;lt;CGI::Session:0x2b6b6fcfe918&amp;gt;&lt;br&gt;    /disk1/home/slugs/81454_93ad4da_f9e7/mnt/vendor/plugins/hoptoad_notifier/lib/hoptoad_notifier/catcher.rb:59:in `request_data_for_hoptoad'&lt;br&gt;&lt;br&gt;Are there any known workarounds for the moment?&lt;br&gt;Thanks</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">adamwilson</dc:creator><pubDate>Wed, 11 Nov 2009 19:09:39 -0000</pubDate></item><item><title>Re: Heroku | Tech: Sending email with Gmail</title><link>http://blog.heroku.com/archives/2009/11/9/tech_sending_email_with_gmail/#comment-22574991</link><description>But the whole point of Heroku is to save developers the trouble of thinking&lt;br&gt;about implementation details like these. As long as the abstraction works,&lt;br&gt;I'd prefer to spend my time making my application better, rather than&lt;br&gt;learning how the addon does its job.&lt;br&gt;&lt;br&gt;Anyway, you commented on your Google Group that you were considering killing&lt;br&gt;the Gmail addon, and I'd like to urge you to reconsider. Developers can&lt;br&gt;always go the plugin route (which is what I did since I implemented mail in&lt;br&gt;my apps before you had the addon) if they want to do extra work, but why not&lt;br&gt;give them the option of something easier?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">RogerPodacter</dc:creator><pubDate>Tue, 10 Nov 2009 14:58:28 -0000</pubDate></item><item><title>Re: Heroku | Tech: Sending email with Gmail</title><link>http://blog.heroku.com/archives/2009/11/9/tech_sending_email_with_gmail/#comment-22524963</link><description>These instructions are actually exactly what the gmail add-on does.  We've heard from a lot of people they were concerned that the add-on was doing some magic, so we wanted to explain what's going on.  This also gives you an easy route to use Gmail even if you're not on Heroku.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">teich</dc:creator><pubDate>Tue, 10 Nov 2009 02:22:02 -0000</pubDate></item><item><title>Re: Heroku | Tech: Sending email with Gmail</title><link>http://blog.heroku.com/archives/2009/11/9/tech_sending_email_with_gmail/#comment-22512563</link><description>What's the difference between these instructions and the instructions in &lt;a href="http://docs.heroku.com/gmail-smtp?" rel="nofollow"&gt;http://docs.heroku.com/gmail-smtp?&lt;/a&gt; (The Gmail addon seems like a cleaner solution (no need for a Rails plugin))</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">RogerPodacter</dc:creator><pubDate>Mon, 09 Nov 2009 20:53:29 -0000</pubDate></item><item><title>Re: Heroku | Push and Pull Databases To and From Heroku</title><link>http://blog.heroku.com/archives/2009/3/18/push_and_pull_databases_to_and_from_heroku/#comment-22462579</link><description>does pull replace data in the target database?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">omnivore</dc:creator><pubDate>Mon, 09 Nov 2009 13:43:34 -0000</pubDate></item><item><title>Re: Heroku | Add-ons Launch</title><link>http://blog.heroku.com/archives/2009/10/29/add_ons_launch/#comment-22010429</link><description>It works now.  :)  The simplicity of installing a new add-on to your app is just mind blowing.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ladyfox14</dc:creator><pubDate>Thu, 05 Nov 2009 23:32:25 -0000</pubDate></item><item><title>Re: Heroku | Push and Pull Databases To and From Heroku</title><link>http://blog.heroku.com/archives/2009/3/18/push_and_pull_databases_to_and_from_heroku/#comment-21966782</link><description>I have a database where the `id` column is an UUID. This is completely ignored&lt;br&gt;by ActiveRecord's schema serializer, it turns out -- there is thus no way for me to&lt;br&gt;use this very nice feature.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">solidsnack</dc:creator><pubDate>Thu, 05 Nov 2009 15:14:08 -0000</pubDate></item><item><title>Re: Heroku | The best camera is...</title><link>http://blog.heroku.com/archives/2009/9/25/the_best_camera_is/#comment-21725358</link><description>This is awesome guys! I've been following Chase for a few months now ever since getting into Photography and was wondering how much traffic he was getting from the iPhone app.  &lt;br&gt;&lt;br&gt;Funny thing is, as soon as I saw his site, I wanted to do something with the .json he was returning, so I built: &lt;a href="http://www.thebestcameraonblack.com/" rel="nofollow"&gt;http://www.thebestcameraonblack.com/&lt;/a&gt; as a sinatra app... and then immediately hosted it on Heroku ... total time: 25min from writing the first line of code to fully deployed</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cgrusden</dc:creator><pubDate>Mon, 02 Nov 2009 21:27:08 -0000</pubDate></item><item><title>Re: Heroku | Add-ons Launch</title><link>http://blog.heroku.com/archives/2009/10/29/add_ons_launch/#comment-21491043</link><description>So this is a pretty sweet set of features, and I went ahead and added the New Relic addon, but...how do I remove addons?? (I don't actually need it yet)  I can't find a way through the web interface -- shouldn't be that hard, but it doesn't seem possible.  Or at least, not as intuitive as adding addons.&lt;br&gt;&lt;br&gt;Thanks, keep up the great work!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nanodeath</dc:creator><pubDate>Sat, 31 Oct 2009 21:23:59 -0000</pubDate></item><item><title>Re: Heroku | Add-ons Launch</title><link>http://blog.heroku.com/archives/2009/10/29/add_ons_launch/#comment-21356903</link><description>It looks like the 3 minute overview video is not available?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">barmstrong</dc:creator><pubDate>Fri, 30 Oct 2009 11:40:15 -0000</pubDate></item><item><title>Re: Heroku | Heroku Directions</title><link>http://blog.heroku.com/archives/2009/10/22/heroku_directions/#comment-20862229</link><description>Could you share a little bit about the monitoring services you have under development?  I love using Heroku but without monitoring I've only been able to use it for staging and demo environments.&lt;br&gt;&lt;br&gt;I have an idea on hooking up &lt;a href="http://scoutapp.com" rel="nofollow"&gt;scoutapp.com&lt;/a&gt;, but I'd prefer using something supported by Heroku.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">edavis10</dc:creator><pubDate>Fri, 23 Oct 2009 11:33:13 -0000</pubDate></item><item><title>Re: Heroku | Heroku Casts: Maintenance Mode</title><link>http://blog.heroku.com/archives/2009/10/19/heroku_casts_maintenance_mode/#comment-20675423</link><description>You guys are truly awesome.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ben_hill</dc:creator><pubDate>Tue, 20 Oct 2009 22:55:48 -0000</pubDate></item><item><title>Re: Heroku | Heroku Casts: Maintenance Mode</title><link>http://blog.heroku.com/archives/2009/10/19/heroku_casts_maintenance_mode/#comment-20656929</link><description>That's an interesting idea.  We'll add that to the backlog!  Thanks.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">teich</dc:creator><pubDate>Tue, 20 Oct 2009 18:29:07 -0000</pubDate></item><item><title>Re: Heroku | Heroku Casts: Maintenance Mode</title><link>http://blog.heroku.com/archives/2009/10/19/heroku_casts_maintenance_mode/#comment-20591343</link><description>What about throwing an app into maintenance mode if it crashes on startup?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryandotsmith</dc:creator><pubDate>Mon, 19 Oct 2009 19:31:46 -0000</pubDate></item><item><title>Re: Heroku | Announcing Huge Growth and New CEO</title><link>http://blog.heroku.com/archives/2009/10/15/announcing_huge_growth_and_new_ceo/#comment-20166377</link><description>Amqp amqp amqp!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">amqp</dc:creator><pubDate>Thu, 15 Oct 2009 19:52:47 -0000</pubDate></item><item><title>Re: Heroku | Announcing Huge Growth and New CEO</title><link>http://blog.heroku.com/archives/2009/10/15/announcing_huge_growth_and_new_ceo/#comment-20160245</link><description>Congrats!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">eoghanmccabe</dc:creator><pubDate>Thu, 15 Oct 2009 18:59:16 -0000</pubDate></item><item><title>Re: Heroku | Config Vars for Deploy-Specific Settings</title><link>http://blog.heroku.com/archives/2009/4/7/config-vars/#comment-20159512</link><description>why not just add .gitignore to the project root and include&lt;br&gt;config/amazon_keys.yml&lt;br&gt;&lt;br&gt;Git will not commit this file if that entry is present.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tmatheson</dc:creator><pubDate>Thu, 15 Oct 2009 18:47:57 -0000</pubDate></item><item><title>Re: Heroku | Push and Pull Databases To and From Heroku</title><link>http://blog.heroku.com/archives/2009/3/18/push_and_pull_databases_to_and_from_heroku/#comment-20142148</link><description>It works well, but uploads are very slow. This method must not use compression.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">WT</dc:creator><pubDate>Thu, 15 Oct 2009 14:46:20 -0000</pubDate></item><item><title>Re: Heroku | Announcing Huge Growth and New CEO</title><link>http://blog.heroku.com/archives/2009/10/15/announcing_huge_growth_and_new_ceo/#comment-20122334</link><description>Congrats, sounds like great growth for the company and exciting change for the team. Hoping to see some new great features soon.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">wastedbrains</dc:creator><pubDate>Thu, 15 Oct 2009 10:16:47 -0000</pubDate></item><item><title>Re: Heroku | Announcing Huge Growth and New CEO</title><link>http://blog.heroku.com/archives/2009/10/15/announcing_huge_growth_and_new_ceo/#comment-20121765</link><description>Great news! Especially the one about a new status site :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xhr</dc:creator><pubDate>Thu, 15 Oct 2009 10:05:09 -0000</pubDate></item><item><title>Re: Heroku | Announcing Huge Growth and New CEO</title><link>http://blog.heroku.com/archives/2009/10/15/announcing_huge_growth_and_new_ceo/#comment-20108611</link><description>Thanks for your comments Harry.  You're absolutely right - we've got a new status site we're going to be using moving forward:&lt;br&gt;&lt;a href="http://status.heroku.com/" rel="nofollow"&gt;http://status.heroku.com/&lt;/a&gt;&lt;br&gt;&lt;br&gt;We did have a brief issue yesterday affecting some apps, and unfortunately we hadn't launched this site yet.  We have just completed our analysis, and posted the details to the status site.&lt;br&gt;&lt;br&gt;Moving forward, we will use that site as the main channel for service status updates.  It is hosted on a separate provider from Heroku's main operations.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jamesheroku</dc:creator><pubDate>Thu, 15 Oct 2009 05:00:09 -0000</pubDate></item></channel></rss>