Peeking into the Rails 2.3.8, params parsing is handled by
ActionContoller::ParamsParser, which is located in
actionpack/lib/action_controller/params_parser.rb:
https://github.com/rails/rails/blob/240f4e944cd90fca138aba8467456043952110cc/actionpack/lib/action_controller/params_parser.rb
ParamsPar
I've heard good things about Blitz.io but haven't tried it yet. I'm
sure it's good.
If for any reason you're looking for an alternative, we'd had good
luck with Apache Bench and the New Relic add-on:
http://robots.thoughtbot.com/post/8392002973/7-minute-ab-impatient-mans-load-tests-for-a-heroku
You could try a script like Kumade and patch it so that it always does
a restart after migrating:
https://github.com/thoughtbot/kumade
On Mon, Aug 8, 2011 at 2:42 PM, John Beynon wrote:
> This isn't something that has affected myself but in selling Heroku to the
> other devs at my workplace one
Hi Michael,
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.
Dan Croak
I'm using mobile-fu on a few Rails apps on Heroku:
https://github.com/brendanlim/mobile-fu
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.
On
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 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
phone, we
had production access.
On Fri, Feb 4, 2011 at 12:54 PM, Miles Smith wrote:
>
>
> How does one remove themselves from the sandbox?
>
> On Fri, Feb 4, 2011 at 9:51 AM, Dan Croak wrote:
>
>> That doesn't appear to be true once you've moved ou
ou set 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 wrote:
> That doesn't appear to be true once you&#x
That doesn't appear to be true once you've moved out of their sandbox and
into the production environment. I just tested this a few seconds ago,
sending an email via Amazon SES from a Rails app to an email that has never
received an SES email before.
The user received only the email from my app, n
I ran into the same thing earlier today. "Solved" it by switching to
RestClient.
On Nov 10, 2010, at 6:38 PM, guillaume fradin > wrote:
this error prevents me from deploying. Has any experienced this?
Installing patron (0.4.10) with native extensions /usr/
ruby1.8.7/lib/ruby/site_ru
In our config/newrelic.yml, we have:
disable_mongodb: true
In config/initializers/mongo_method_tracers, we have:
Rails.configuration.after_initialize do
Mongo::Cursor.class_eval do
add_method_tracer :refill_via_get_more,
'Database/#{collection.name}/get_more'
add_method_tracer :count
There are some troubleshooting suggestions on this page:
http://docs.heroku.com/ps
On Mon, Oct 4, 2010 at 1:04 PM, Brandon Casci 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?
>
> On Thu, Sep 30,
On Thu, Aug 26, 2010 at 11:30 AM, marcel wrote:
> Also, it often takes 10-20 seconds to get a page to load after a
> period of inactivity, compared to lightning speed for the production
> app.
I can't find it in the docs, but I'm pretty sure that your dyno will
"spin down", or "go to sleep", or
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:
heroku ps
On Thu, Jul 29, 2010 at 11:10 AM, Alex Chaffee wrote:
> I wrote a simple Heroku app to do service monitoring. It uses
> DelayedJob to queue up repe
Howdy,
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
faults:
https://rails.lighthouseapp.com/projects/8994/tickets/5193-segmentation-fault-on-rake-dbcreate-multiple-rubies-multiple-dbs
The fix in develop
I think this is an "aws-s3 gem doesn't support European buckets by
default" thing.
Try setting this constant in your config/environment.rb:
AWS::S3::DEFAULT_HOST = "s3-eu-west-1.amazonaws.com"
Discussion here:
http://github.com/marcel/aws-s3/issues#issue/4
On Jul 25, 3:23 pm, Mateus wrote:
>
t push g...@heroku.com:myprodapp.git master:master
> git push g...@heroku.com:mystagingapp.git edge:master
>
> I could be a little off, but that's the basic idea. Check out 'git
> push --help' for more details. Also http://grb.rubyforge.org is
> helpful for dealing with
whitelist of allowed
> value types instead of a blacklist of disallowed value types. Adding
> Method/Proc to the current list of disallowed types would also solve
> this issue but it will happen again with some other object. It's
> becoming a very common pattern in Rack to add various ty
18 matches
Mail list logo
