>From what I have heard and seen, the only way to purge the cache is to
git push.
On Feb 18, 10:40 am, railsnerd wrote:
> Is this possible?
>
> Any hacks, atleast?
>
> Does the Lacquer gem work with Heroku?
>
> Thanks for any tips :)
--
You received this message because you are subscribed to t
t your dyno
> terminates after 30 seconds so you don't get this odd behavior.
>
> --
> Oren Teich
>
>
>
>
>
>
>
> On Wednesday, February 16, 2011 at 12:13 PM, Tim W wrote:
> > Wow.. that does say the mesh will hold a request until an app is
> > availa
nt
> problem.
>
> Neil Middletonhttp://about.me/neilmiddleton
>
>
>
>
>
>
>
> On Wednesday, 16 February 2011 at 18:01, Tim W wrote:
> > It is not identical to what Heroku is providing.. The Heroku mesh
> > seems to blindly sends a request to a dyno, no
hat take longer than 30 seconds.
>
> Neil Middletonhttp://about.me/neilmiddleton
>
>
>
>
>
>
>
> On Wednesday, 16 February 2011 at 17:46, Tim W wrote:
> > Passenger... imho handles this better then Heroku
>
> >http://www.modrails.com/documentation/Users%2
umentation/Users%20guide%20Apache.html#_re...
>
> Neil Middletonhttp://about.me/neilmiddleton
>
>
>
>
>
>
>
> On Wednesday, 16 February 2011 at 17:29, Tim W wrote:
> > I guess I am just used to using passenger which uses a global queue,
> > making a single long
p://about.me/neilmiddleton
>
>
>
>
>
>
>
> On Wednesday, 16 February 2011 at 16:55, Tim W wrote:
> > Thanks, I will give rack-timeout a try.
>
> > So what it seems like is that the routing mesh is not as sophisticated
> > as Heroku leads on?
>
>
e/neilmiddleton
>
>
>
>
>
>
>
> On Wednesday, 16 February 2011 at 16:42, Tim W wrote:
> > The Heroku website claims:
>
> >http://heroku.com/how/dyno_grid_last#3
> > "If a dyno is unresponsive for any reason (user bugs, long requests,
> > or hi
The Heroku website claims:
http://heroku.com/how/dyno_grid_last#3
"If a dyno is unresponsive for any reason (user bugs, long requests,
or high load), other requests will be routed around it."
In my experience, this does not seem to be the case. We have several
admin features in our app that when
Disregard.. I traced it back to something wrong with the Compass gem.
-tim
On Sep 12, 6:15 pm, Tim W wrote:
> Appears to be something wrong with it..
>
> From the heroku console>> Account.first.to_json
>
> => "\"#\""
>
> I don't get the err
Appears to be something wrong with it..
>From the heroku console
>> Account.first.to_json
=> "\"#\""
I don't get the error on my local machine. A bug or an I doing
something wrong?
-timw
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to th
Trying to get our app up and running on Heroku and am having some
issues with the models that connect to a 2nd remote database.
I get the error:
:in `establish_connection': wawd database is not configured
(ActiveRecord::AdapterNotSpecified)
The database is configured in database.yml and currently
11 matches
Mail list logo
