You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to
, but that's the basic idea. Check out 'git
push --help' for more details. Also http://grb.rubyforge.org is
helpful for dealing with remote branches.
You received this message because you
I think this is an aws-s3 gem doesn't support European buckets by
Try setting this constant in your config/environment.rb:
AWS::S3::DEFAULT_HOST = s3-eu-west-1.amazonaws.com
On Jul 25, 3:23 pm, Mateus
I was messing with a Rails 3 app on REE Heroku. Things started out
well but as I added dependencies to my Gemfile, I started getting seg
The fix in
Only time I've had issues with workers is when I messed up something
on my side so that I was causing DJ to crash. I debugged it by doing:
On Thu, Jul 29, 2010 at 11:10 AM, Alex Chaffee a...@cohuman.com wrote:
I wrote a simple Heroku app to do service monitoring. It uses
There are some troubleshooting suggestions on this page:
On Mon, Oct 4, 2010 at 1:04 PM, Brandon Casci bran...@loudcaster.com wrote:
I can only offer commiseration because I'm in the same position as you ;)
Please let me know what they say.
What do your jobs do?
In our config/newrelic.yml, we have:
In config/initializers/mongo_method_tracers, we have:
I ran into the same thing earlier today. Solved it by switching to
On Nov 10, 2010, at 6:38 PM, guillaume fradin guillaumefra...@googlemail.com
this error prevents me from deploying. Has any experienced this?
Installing patron (0.4.10) with native extensions
the sending user's email to the
Reply-To header so the receiver can just reply normally.
We decided to remove the Reply-To feature for now.
On Fri, Feb 4, 2011 at 12:51 PM, Dan Croak dcr...@thoughtbot.com wrote:
That doesn't appear to be true once you've moved out of their sandbox
the phone, we
had production access.
On Fri, Feb 4, 2011 at 12:54 PM, Miles Smith mi...@vimae.com wrote:
How does one remove themselves from the sandbox?
On Fri, Feb 4, 2011 at 9:51 AM, Dan Croak dcr...@thoughtbot.com wrote:
That doesn't appear to be true once you've moved out
Amazon has now removed the email address verification requirement of the
Reply-To header. Sweet!
On Fri, Feb 4, 2011 at 12:53 PM, Dan Croak dcr...@thoughtbot.com wrote:
The only problem we've seen so far is not being able to use the Reply-To
header because THAT email address must be verified
I'm using mobile-fu on a few Rails apps on Heroku:
It does device detection by checking the user agent against a giant regex.
It also provides a mobile mime type so you can put your mobile-specific views
in their own foo.mobile.erb views if you want.
I imagine that the addon is no longer listed because of the EOL of the
Hoptoad Beta addon. Did you receive an email recently from Heroku like
the one below my signature?
You shouldn't have received an application error from Hoptoad, though.
We'll look into that.
You could try a script like Kumade and patch it so that it always does
a restart after migrating:
On Mon, Aug 8, 2011 at 2:42 PM, John Beynon j...@beynon.org.uk wrote:
This isn't something that has affected myself but in selling Heroku to the
other devs at
Peeking into the Rails 2.3.8, params parsing is handled by
ActionContoller::ParamsParser, which is located in
Mail list logo