+1 for iframe/javascript solution
I feel like the same system could be used to improve the custom
maintenance mode page as well.
I tested it out on my staging app the other day, and it took 15
minutes before the ugly default page was replaced by my custom page.
Thats just too long! My biggest
+1 -- I've been waiting for this one for a loong time.
On Sep 16, 2:06 am, Daniele to...@vitamino.it wrote:
A separate branch or a dedicated folder are not a solutions.
When a system wide problem occurs (as 2 days ago) the dyno grid and
probably the routing mesh too are broken, so all the
Hi,
as you can see from the status page in the past 2 days Heroku had a
lot of problems that resulted in Timeout connection and Backlog Too
Deep error pages. This two pages have a message specifically
addressed to the administrator that is not acceptable in a production
site. We need to have
+1 Maybe the generic page could be a fail Koi
On Wed, Sep 15, 2010 at 7:31 AM, Daniele to...@vitamino.it wrote:
Hi,
as you can see from the status page in the past 2 days Heroku had a
lot of problems that resulted in Timeout connection and Backlog Too
Deep error pages. This two pages have a
+ 1 on this also. like the idea about the iframe
On Wed, Sep 15, 2010 at 9:02 AM, Jeff Schmitz
jeffrey.j.schm...@gmail.comwrote:
+1 Maybe the generic page could be a fail Koi
On Wed, Sep 15, 2010 at 7:31 AM, Daniele to...@vitamino.it wrote:
Hi,
as you can see from the status page in the
I like the idea too,
but maybe I don't wan't to set up an extra heroku app or shared host for an
static html page only,
maybe it would be nice if you can choose to take the iframe and a textinput,
where you can insert plain html.
Daniel
Am 15.09.2010 um 16:55 schrieb Adrian Cuadros:
+ 1 on
I've suggested in the past having a separate branch in your repo called
errorpages or something, which has a few static HTML pages. Push that
branch to Heroku, and it can use those files to serve errors.
On Wed, Sep 15, 2010 at 7:58 AM, Daniel Spangenberg
daniel.spangenb...@googlemail.com wrote:
Why have a separate branch? Heroku can just tell us where to put them
in the folder hierarchy and they'll grab them from there.
If I were designing this I'd say to create a top level directory in
your project called errors or heroku_error_pages or something like
that. Then name you're files
