[LRUG] Fwd: Rendering maintenance pages?

[Daniel Barlow]

fail of "reply to all"

On 27 June 2013 10:35, Paul Robinson <paul at 32moves.com> wrote:

> On 27 Jun 2013, at 09:14, Joel Chippindale <joel.chippindale at gmail.com>
> wrote:
>
> > The bit that I was wondering about was finding a clean and simple way of
> getting a rake task to render the maintenance page (and perhaps 500 and 404
> response pages too) from erb templates to the filesystem, whilst still be
> able to take advantage of asset packaging, name route helper methods etc.
>
>
> If you're in the middle of upgrading the app, doing a bundle install, an
> asset precompile, etc. you do not want your maintenance pages accessing
> that app or those resources.
>
> You want a separate area of disk holding those assets that
> nginx/apache/whatever is going to rewrite all requests to until you're done.
>

I think you're actually agreeing with each other here: Joel is talking
about a rake task and a static page, which presumably would be written to
this "separate area of disk" to be served directly by nginx/your upstream
proxy next time the app is brought down, but he wants it to be produced
using the same layout, styles and general look & feel as the app itself and
to stay in sync when the app changes.  It seems like this is the kind of
thing the asset precompiler should be able to do, but I've no  idea how.


-dan

-- 
dan at telent.net
http://ww.telent.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130627/68f5f886/attachment.html>