I've just got a working demo up of ActionMailbox.
One thing that caught me out when I moved from dev to a Heroku + mailgun
app was that with a real email (from gmail) it's a multipart message and
you have to access the content differently in that case.
I know the conductor pages are probably st
turns out it was the method name 'dispatch' that was causing the
issue.
On Jul 8, 9:25 pm, johnb wrote:
> I'm trying out globbing for the first time,
>
> I have the route
>
> match '*path' => 'request#dispatch'
>
> defined a
I'm trying out globbing for the first time,
I have the route
match '*path' => 'request#dispatch'
defined and a scaffolded request controller with dispatch method and
accompanying scaffolded default view yet I get;
ArgumentError in RequestController#dispatch
wrong number of arguments (2 for 0)
turns out to be nothing to do with Herokupointing the finger too
early :)
Seems to be a problem with Rails 3 Namescope routes (/admin) and the
right_aws gem declared in both a production and staging environment in
the Gemfile.
John.
On Jun 24, 11:51 am, johnb wrote:
> It seems to
It seems to be dependent on the environment the application is running
in, development seems to work, I'm seeing a routing failure locally in
production mode the same as Neil details above and also a 'staging'
environment that I'm also running on Heroku
On Jun 23, 6:14 pm, jo
I have exactly the same problem, works locally (osx) but when deployed
to Heroku I get a similar error has Neil has detailed above
Rails 3 b4.
John.
On Jun 22, 10:09 am, Neil wrote:
> Anyone? From what I can see from the guides, what I am doing here is
> correct (http://guides.rails.info/routi
You've probably already figured it out, but this looks workable:
# See this page for some of the statement-related settings:
# http://www.postgresql.org/docs/8.3/static/runtime-config-client.html
def setStatementTimeout milliseconds
query = "SET statement_timeout = #{milliseconds};"
7 matches
Mail list logo
