Re: [PATCH] pgarchives: settings: set DEBUG to False by default

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
Cc: PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] pgarchives: settings: set DEBUG to False by default
Date: 2026-10-08 08:40:59
Message-ID: CABUevEwd3uD=QKiZku7MGj3BRWfmTXqPYLjW9LPBpwfR_ShiMg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Wed, 7 Oct 2026 at 17:27, Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
wrote:

> Unlike pglister and pgweb, pgarchives has DEBUG set to True by default.
> This is dangerous and could lead to deployments being made with this
> default settings in case of an oversight (if it's not explicitly overriden
> in local_settings.py).
> Set it to False by default, matching pglister and pgweb.
>

Makes sense. Secure deployments should of course always set it in
local_settings.py to be on the safe saide, but diong it by default is also
good. Thus - applied. thanks!
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2026-10-08 09:00:51 Re: [PATCH] pglister: Filter pending subscriptions out of the list memberships page
Previous Message Melanie Plageman 2026-10-08 00:02:40 Re: Introduce contributor badges