+1 -- I've been waiting for this one for a loooooong time. On Sep 16, 2:06 am, Daniele <[email protected]> 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 "logic" part of > the system is unavailable. Heroku can only serve a generic page. > Perhaps it can personalize it with the request headers (es. domain > name) but no more. > So an iframe or an ajax setup is the only way. > > Different address for the message 'backlogged to deep" that could be > personalized using a specific folder/file. But we have to point out > when it pop up: during the system's problem phase I get a lot of these > messages while the git repo was not probably accessible. So I will > prefer an iframe/ajax solution in this case too. > > Daniele > > On Sep 15, 7:19 pm, Mike Abner <[email protected]> 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.
-- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
