Re: Heroku down time today, about 30 minutes total
So, 3 nine's is what to expect from Heroku? On Oct 28, 3:50 am, Peter Marklund wrote: > Regardless with hosting option you choose you will have downtime. I > have found more often than not the reason is to do with infrastructure > like power, networking, hardware, routing etc. that will most likely > be out of your control. I think the downtime I've seen with Heroku is > tolerable and you shouldn't necessarily assume you'll have less > downtime if you move somewhere else. > > Peter > > On Oct 27, 9:46 pm, oma wrote: > > > unexpected downtown is way different than planned downtown. This is > > really discomforting. I'm not looking forward in moving my production > > app to more stable place... heroku should really answer this. > > > On Oct 27, 7:19 pm, Jimmy Thrasher wrote: > > > > Interesting. So, back of the envelope, from a dev perspective: > > > > ruby-1.8.7-p302 > elapsed = (Time.local(2010,10,26,16) - > > > Time.local(2010,8,1)) / 60 > > > =>124800.0 > > > ruby-1.8.7-p302 > (elapsed - 45 - 28 - 45) / elapsed > > > => 0.999054487179487 > > > > About 99.9% uptime over the elapsed time. > > > > It's still way cheaper for me to use Heroku, but the cost of 30 minutes of > > > downtime in a month is fairly low. Folks with higher uptime requirements > > > are likely just going to have to shell out the $$$ no matter which way you > > > slice it. > > > > Jimmy > > > > On Wed, Oct 27, 2010 at 12:54 PM, John Norman wrote: > > > > Below is the data I have for one app (similar data from two other apps). > > > > > So, for September, 28 minutes of downtime . . . better than 3 nines: > > > >http://en.wikipedia.org/wiki/High_availability#Percentage_calculation > > > > > But I would much rather report to my customers official data from > > > > Heroku. > > > > > The times below are central time zone, I think. > > > > > AUGUST - Total unavailable minutes: 45 > > > > > unavail at avail at elapsed > > > > 8/4/2010 17:06:00 8/4/2010 17:51:00 0:45:00 > > > > > SEPTEMBER - Total unavailable minutes: 28 > > > > > 9/13/2010 8:46:00 9/13/2010 8:55:00 0:09:00 > > > > 9/13/2010 14:26:00 9/13/2010 14:36:00 0:10:00 > > > > 9/21/2010 1:16:00 9/21/2010 1:21:00 0:05:00 > > > > 9/28/2010 22:26:00 9/28/2010 22:30:00 0:04:00 > > > > > OCTOBER - Total unavailable minutes so far: 45 > > > > > 10/4/2010 15:41:00 10/4/2010 15:51:00 0:10:00 > > > > 10/5/2010 11:56:00 10/5/2010 12:01:00 0:05:00 > > > > 10/26/2010 12:16:00 10/26/2010 12:26:00 0:10:00 > > > > 10/26/2010 14:41:00 10/26/2010 14:46:00 0:05:00 > > > > 10/26/2010 15:21:00 10/26/2010 15:36:00 0:15:00 > > > > > On Wed, Oct 27, 2010 at 9:53 AM, Jimmy Thrasher > > > > wrote: > > > > >> I'd be curious to find out what the actual uptime percentage is, and > > > >> what > > > >> it would cost you to maintain that on a different platform with > > > >> comparable > > > >> services. :) > > > > >> Jimmy > > > > >> On Wed, Oct 27, 2010 at 9:55 AM, JDeville > > > >> wrote: > > > > >>> Al, I'm afraid Heroku's had a fair bit of downtime since I've joined > > > >>> earlier this year. The status link mattsly gave you paints a pretty > > > >>> grim picture. I figure I'll probably have to come up with something > > > >>> else once my site's uptime becomes important to me. I'm hoping they > > > >>> stop adding new features, and instead pour themselves into stability. > > > > >>> On Oct 27, 8:11 am, mattsly wrote: > > > >>> > You can browse the incident archive > > > >>> > here:http://status.heroku.com/past > > > > >>> > Most of the issues seems to be related to tooling, but there was at > > > >>> > least one other case of app outage earlier in the month (Oct. 4) > > > > >>> > Does Heroku publish uptime numbers? Does anyone running an app in > > > >>> > production (I'm still not yet...) have app uptime numbers they're > > > >>> > willing to share? > > > > >>> > On Oct 26, 7:03 pm, Shane Becker > > > >>> > wrote: > > > > >>> > > > How can we be sure this won't happen again? > > > > >>> > > No > > > > >>> -- > > > >>> You received this message because you are subscribed to the Google > > > >>> Groups > > > >>> "Heroku" group. > > > >>> To post to this group, send email to her...@googlegroups.com. > > > >>> To unsubscribe from this group, send email to > > > >>> heroku+unsubscr...@googlegroups.com > > > >>> . > > > >>> For more options, visit this group at > > > >>>http://groups.google.com/group/heroku?hl=en. > > > > >> -- > > > >>+1-919-627-7546 > > > > >> -- > > > >> You received this message because you are subscribed to the Google > > > >> Groups > > > >> "Heroku" group. > > > >> To post to this group, send email to her...@googlegroups.com. > > > >> To unsubscribe from this group, send email to > > > >> heroku+unsubscr...@googlegroups.com > > > >> . > > > >> For more options, visit this group at > > > >>http://groups.google.com/group/heroku?hl=en. > > > > > -- > > > > You received this message b
Re: Full Logging Solutions
On Oct 28, 2010, at 3:13 PM, Peter Marklund wrote: > I've experimented with logging to MongoDB lately and I've found it to > work really well. The MongoDB performance along with its query > capabilities opens up a lot of possibilities. I'm doing my logging to > MongoHQ now through a Rack middleware and am monitoring the > performance (time overhead) of the logging and it's looking really > good so far. I've packaged up my code in a gem: Good stuff. We're doing some similar things. You may want to look at Mongo's capped collections for some of your logging if you're not already: The natural ordering and fixed max size can be really useful. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Full Logging Solutions
I've experimented with logging to MongoDB lately and I've found it to work really well. The MongoDB performance along with its query capabilities opens up a lot of possibilities. I'm doing my logging to MongoHQ now through a Rack middleware and am monitoring the performance (time overhead) of the logging and it's looking really good so far. I've packaged up my code in a gem: http://github.com/peter/request_log Cheers Peter On Oct 21, 12:11 am, Eric Anderson wrote: > On Oct 20, 11:18 am, Jeff Schmitz wrote: > > > Another question would be does Heroku need anything written to the rails > > log? Would your patch cause Herkou any issues? > > I would think not as Heroku is more "rack" focused and Rails is just a > framework that can run on "rack". That being said there is some > special mojo for Rails (such as setting up the database connection, > ActionMailer, etc). So the only real way to know is to test. I will be > developing this concept and testing it shortly so will report back > what I find. > > Eric -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Bundler upgrade to 1.0.3 to support BUNDLE_WITHOUT?
Yeah, it does indeed appear to be working. Maybe I just didn't realize that before. I guess they patched bundler. Maybe the reason I didn't notice was that I was hoping for a bigger drop in slug size, I'm still at 12.4MB for a Rails app with only a handful of gem dependencies. Hmm, I think it's because I recently started using MongoDB. The mongo gem needs bson_ext for performance and bson_ext includes an 8.4MB jar file. Completely useless to me of course... Thanks! Peter On Oct 28, 6:11 pm, Chris Hanks wrote: > Yep, it's worked for me for weeks too. > > On Oct 28, 7:28 am, marcel wrote: > > > BUNDLE_WITHOUT is currently working for me. It magically started being > > recognized a few weeks ago. From my heroku config output: > > > BUNDLE_WITHOUT => test development > > > And when I deploy: > > > -> Heroku receiving push > > -> Rails app detected > > -> Gemfile detected, running Bundler version 1.0.0 > > Unresolved dependencies detected; Installing... > > Using --without test development > > Fetching source index forhttp://rubygems.org/ > > ... -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Could not find a valid gem 'source'
I don't know it this will help, but my Gemfile looks quite different. First, the sources line is like this: source 'http://gemcutter.org' probably both notations are valid though. The problematic part is probably your Authlogic line. Mine looks like this: gem 'authlogic', :git => 'http://github.com/binarylogic/authlogic.git', '2.1.3' As you can see, I include a complete url to a concrete git file instead of just referencing the repository like you do. I hope that helps. On Thu, Oct 28, 2010 at 6:55 AM, jhubert wrote: > For some reason I can't deploy my Rails 3 app. My Gemfile looks like > this: > > source :rubygems > > gem 'rails', '3.0.1' > > gem 'sqlite3-ruby', :require => 'sqlite3' > > gem 'authlogic', :git => 'git://github.com/odorcicd/ > authlogic.git', :branch => 'rails3' > gem 'acts_as_commentable' > gem 'activemerchant' > > gem 'jquery-rails' > > and the error message looks like this: > > -> Heroku receiving push > -> Rails app detected > > -> Installing gem source from http://rubygems.org > ERROR: Could not find a valid gem 'source' (> 0) in any > repository > ! Heroku push rejected, failed to install gem > > > Any ideas what might cause this? I am running on the bamboo-ree stack > using Rails 3.0.1 > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Could not find a valid gem 'source'
For some reason I can't deploy my Rails 3 app. My Gemfile looks like this: source :rubygems gem 'rails', '3.0.1' gem 'sqlite3-ruby', :require => 'sqlite3' gem 'authlogic', :git => 'git://github.com/odorcicd/ authlogic.git', :branch => 'rails3' gem 'acts_as_commentable' gem 'activemerchant' gem 'jquery-rails' and the error message looks like this: -> Heroku receiving push -> Rails app detected -> Installing gem source from http://rubygems.org ERROR: Could not find a valid gem 'source' (> 0) in any repository ! Heroku push rejected, failed to install gem Any ideas what might cause this? I am running on the bamboo-ree stack using Rails 3.0.1 -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: SOLVED: Has anyone got pony working with gmail on heroku?
The example below works, it now uses via options instead of smtp, also
the body is now included, if some one out there is wondering what
ENV['TO_EMAIL'] is. These are environment variables that are easily
setup locally and on heroku. Its all explained here
http://docs.heroku.com/config-vars
Pony.mail :to => ENV['TO_EMAIL'],
:from => params[:email],
:subject => params[:subject],
:body => params[:email] +" wrote:\n" +
params[:message],
:via => :smtp,
:via_options => {
:address => 'smtp.gmail.com',
:port => '587',
:user_name => ENV['GMAIL_USER'],
:password => ENV['GMAIL_PASSWORD'],
:authentication => :plain,
:domain => "wavesummit.com"
}
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Heroku Users Group meetup in SF, 11/3 @ 7pm
Greetings, Heroku users! In case you haven’t heard, we wanted to let you know that the first-ever Heroku Users Group (known henceforth and forever more as a HUG) meetup will be held at our offices in San Francisco[1] next Wednesday, November 3rd, at 7pm. We’re inviting everybody, from the developers who deploy to our platform, to business owners who've built companies on top of us, to the add-on providers who provide that extra set of functionality just when you need it, and we’re eager to get everyone in the same room. We can't wait to see the new ideas and developments that will come out of all of us talking at this (and at future) meetups. To kick things off at this first event, though, we’re going to provide the content for you. Adam’s[2] going to kick things off with a quick peek at several features that are in development. He'll be talking about the things many of you have been asking for, and they’ll make deploying complex application much more pleasant. After that, we’ll have a panel of representatives from each of our internal teams -- the people who make Heroku run -- and they’ll be ready and able to answer any questions you have. Curious about the routing mesh? They wrote it! Wondering about the future of Postgres at Heroku? They know! You bring the questions, they’ll bring the answers. As you might be able to tell, we’re getting more and more excited as we close in on the 3rd, and we’re looking forward to seeing you there. Don’t forget to let us know that you’re coming[3], and we’ll see you next week! PS One more thing — we’re co-sponsoring a drinkup at Bloodhound[4] with Basho[5] at 9pm, after the HUG. We’ll have more details on Twitter[6] and at the HUG itself, but be sure to plan to attend both! 1: http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&ll=37.77158,-122.413423&spn=0.010219,0.009205&z=17&msid=116995152408101589563.0004917a8c25b09304f54 2: http://adam.blog.heroku.com/ 3: http://upcoming.yahoo.com/event/7114137 4: http://www.yelp.com/biz/bloodhound-san-francisco-2 5: http://www.basho.com/ 6: http://twitter.com/heroku -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: SOLVED: Has anyone got pony working with gmail on heroku?
Just to follow up this is working, but doesn't include a 'body', and the' from' will always be your gmail. I'll post another example shortly. Cheers, James -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Has anyone got pony working with gmail on heroku?
@ morgoth Is mail gem easier to install than pony? Pony seemed like a good option as it was on the sinatrarb site, and since it was written by Adam at Heroku, I was hoping for an easy install. On Oct 28, 10:45 am, morgoth wrote: > You can also use mail gem. > > You can find my configuration of mail gem in sinatra applicaion in: > > http://github.com/morgoth/kasia/blob/master/app.rb -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Has anyone got pony working with gmail on heroku?
@Pedro, I was able to install the latest version of Pony on heroku without using smtp_tls. I believe (correct me if I am wrong) it uses the latest version of ActionMailer. In my gems manifest I only have the following: sinatra pony haml maruku Any dependencies are automatically installed. Cheers, James On Oct 27, 8:32 am, Pedro Del Gallego wrote: > 2010/10/26 Jimmy : > > > Pony works locally, but on heroku I get the following: > > It's working fine for me. Have you declared the gem "smtp_tls" in > your .gems file? > > Here you have the code.http://gist.github.com/648619 > > > > > > > 2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/ > > spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied > > 2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/ > > spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied > > 2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/ > > spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied > > > Is there a solution or alternative to sending mail from Sinatra using > > Gmail and Pony? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. > > -- > - > Pedro Del Gallego > > Email : pedro.delgall...@gmail.com -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Bundler upgrade to 1.0.3 to support BUNDLE_WITHOUT?
Yep, it's worked for me for weeks too. On Oct 28, 7:28 am, marcel wrote: > BUNDLE_WITHOUT is currently working for me. It magically started being > recognized a few weeks ago. From my heroku config output: > > BUNDLE_WITHOUT => test development > > And when I deploy: > > -> Heroku receiving push > -> Rails app detected > -> Gemfile detected, running Bundler version 1.0.0 > Unresolved dependencies detected; Installing... > Using --without test development > Fetching source index forhttp://rubygems.org/ > ... -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku has a read-only filesystem
What's in your Gemfile? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Bundler upgrade to 1.0.3 to support BUNDLE_WITHOUT?
BUNDLE_WITHOUT is currently working for me. It magically started being recognized a few weeks ago. From my heroku config output: BUNDLE_WITHOUT=> test development And when I deploy: -> Heroku receiving push -> Rails app detected -> Gemfile detected, running Bundler version 1.0.0 Unresolved dependencies detected; Installing... Using --without test development Fetching source index for http://rubygems.org/ ... -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku down time today, about 30 minutes total
Regardless with hosting option you choose you will have downtime. I have found more often than not the reason is to do with infrastructure like power, networking, hardware, routing etc. that will most likely be out of your control. I think the downtime I've seen with Heroku is tolerable and you shouldn't necessarily assume you'll have less downtime if you move somewhere else. Peter On Oct 27, 9:46 pm, oma wrote: > unexpected downtown is way different than planned downtown. This is > really discomforting. I'm not looking forward in moving my production > app to more stable place... heroku should really answer this. > > On Oct 27, 7:19 pm, Jimmy Thrasher wrote: > > > Interesting. So, back of the envelope, from a dev perspective: > > > ruby-1.8.7-p302 > elapsed = (Time.local(2010,10,26,16) - > > Time.local(2010,8,1)) / 60 > > =>124800.0 > > ruby-1.8.7-p302 > (elapsed - 45 - 28 - 45) / elapsed > > => 0.999054487179487 > > > About 99.9% uptime over the elapsed time. > > > It's still way cheaper for me to use Heroku, but the cost of 30 minutes of > > downtime in a month is fairly low. Folks with higher uptime requirements > > are likely just going to have to shell out the $$$ no matter which way you > > slice it. > > > Jimmy > > > On Wed, Oct 27, 2010 at 12:54 PM, John Norman wrote: > > > Below is the data I have for one app (similar data from two other apps). > > > > So, for September, 28 minutes of downtime . . . better than 3 nines: > > >http://en.wikipedia.org/wiki/High_availability#Percentage_calculation > > > > But I would much rather report to my customers official data from Heroku. > > > > The times below are central time zone, I think. > > > > AUGUST - Total unavailable minutes: 45 > > > > unavail at avail at elapsed > > > 8/4/2010 17:06:00 8/4/2010 17:51:00 0:45:00 > > > > SEPTEMBER - Total unavailable minutes: 28 > > > > 9/13/2010 8:46:00 9/13/2010 8:55:00 0:09:00 > > > 9/13/2010 14:26:00 9/13/2010 14:36:00 0:10:00 > > > 9/21/2010 1:16:00 9/21/2010 1:21:00 0:05:00 > > > 9/28/2010 22:26:00 9/28/2010 22:30:00 0:04:00 > > > > OCTOBER - Total unavailable minutes so far: 45 > > > > 10/4/2010 15:41:00 10/4/2010 15:51:00 0:10:00 > > > 10/5/2010 11:56:00 10/5/2010 12:01:00 0:05:00 > > > 10/26/2010 12:16:00 10/26/2010 12:26:00 0:10:00 > > > 10/26/2010 14:41:00 10/26/2010 14:46:00 0:05:00 > > > 10/26/2010 15:21:00 10/26/2010 15:36:00 0:15:00 > > > > On Wed, Oct 27, 2010 at 9:53 AM, Jimmy Thrasher > > > wrote: > > > >> I'd be curious to find out what the actual uptime percentage is, and what > > >> it would cost you to maintain that on a different platform with > > >> comparable > > >> services. :) > > > >> Jimmy > > > >> On Wed, Oct 27, 2010 at 9:55 AM, JDeville wrote: > > > >>> Al, I'm afraid Heroku's had a fair bit of downtime since I've joined > > >>> earlier this year. The status link mattsly gave you paints a pretty > > >>> grim picture. I figure I'll probably have to come up with something > > >>> else once my site's uptime becomes important to me. I'm hoping they > > >>> stop adding new features, and instead pour themselves into stability. > > > >>> On Oct 27, 8:11 am, mattsly wrote: > > >>> > You can browse the incident archive here:http://status.heroku.com/past > > > >>> > Most of the issues seems to be related to tooling, but there was at > > >>> > least one other case of app outage earlier in the month (Oct. 4) > > > >>> > Does Heroku publish uptime numbers? Does anyone running an app in > > >>> > production (I'm still not yet...) have app uptime numbers they're > > >>> > willing to share? > > > >>> > On Oct 26, 7:03 pm, Shane Becker wrote: > > > >>> > > > How can we be sure this won't happen again? > > > >>> > > No > > > >>> -- > > >>> You received this message because you are subscribed to the Google > > >>> Groups > > >>> "Heroku" group. > > >>> To post to this group, send email to her...@googlegroups.com. > > >>> To unsubscribe from this group, send email to > > >>> heroku+unsubscr...@googlegroups.com > > >>> . > > >>> For more options, visit this group at > > >>>http://groups.google.com/group/heroku?hl=en. > > > >> -- > > >>+1-919-627-7546 > > > >> -- > > >> You received this message because you are subscribed to the Google Groups > > >> "Heroku" group. > > >> To post to this group, send email to her...@googlegroups.com. > > >> To unsubscribe from this group, send email to > > >> heroku+unsubscr...@googlegroups.com > > >> . > > >> For more options, visit this group at > > >>http://groups.google.com/group/heroku?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Heroku" group. > > > To post to this group, send email to her...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > heroku+unsubscr...@googlegroups.com > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/heroku?hl=en. > > >
Bundler upgrade to 1.0.3 to support BUNDLE_WITHOUT?
Hi! According to the Heroku documentation at http://docs.heroku.com/bundler you can use this config var setting: heroku config:add BUNDLE_WITHOUT="development test" It will exclude the development and test groups from the bundle install and thus trim down your slug size. However, it didn't seem to work for me. It seems Heroku is still running Bundler 1.0.0 and that BUNDLE_WITHOUT is not supported in that version but is supported in the current 1.0.3 version. Are there any plans to rollout Bundler 1.0.3? Thanks! Peter -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Has anyone got pony working with gmail on heroku?
You can also use mail gem. You can find my configuration of mail gem in sinatra applicaion in: http://github.com/morgoth/kasia/blob/master/app.rb -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
