El 15/07/13 17:15, Jonathan Vanasco escribió:
The easiest way is to enter/exit maintenance mode on the port 80
server ( nginx / apache )
with nginx, it's popular to 'touch' a file to enter maintenance mode
-- so if "/var/www/sites/maintenance" exists, nginx will dispatch to
another set of rules. some people will also just use a different
nginx config file.
using a staging site is better, but if you want to test the same exact
deployment ( which is useful ), i would have nginx/apache host two
separate domains that proxy to the same destination:
* www.domain.com ( public )
* admin.domain.com ( htaccess with a rotating user/pass )
you can set your routing rules so that when you go into maintenance
mode, everything under your "public" site is rewritten to
"/maintenance" [ either apache or pyramid ], but the admin.domain.com
requests aren't changed.
Yes, I think this is the best approach (with ideas proposed by andi).
Thanks to all.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
