public inbox for [email protected]
help / color / mirror / Atom feedFrom: Aditya Toshniwal <[email protected]>
To: Seweryn Zeman <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Subject: Re: pgAdmin Docker gunicorn configurable --access-logfile
Date: Mon, 18 Nov 2019 17:35:21 +0530
Message-ID: <CAM9w-_=4zNuRGbOwy8jRYXWjY5ahHN+v_4zWuotHEGwxdN-=ZA@mail.gmail.com> (raw)
In-Reply-To: <26c74197-524c-432b-b19b-2b3ca36151bd@Spark>
References: <de307365-9113-4492-9b6b-df881fc0ee43@Spark>
<26c74197-524c-432b-b19b-2b3ca36151bd@Spark>
Hi Seweryn,
Kindly raise a feature request here -
https://redmine.postgresql.org/projects/pgadmin4/issues/new
On Mon, Nov 18, 2019 at 4:59 PM Seweryn Zeman <[email protected]>
wrote:
> Hi, me and my company is working with pgAdmin since we decided to use
> pgSql – mostly for development with containers. In this case Docker. While
> starting a docker-compose in dev mode with pgAdmin in stack we can see lots
> of access logs for HTTP and WS which are very irrelevant to us. This makes
> important logs to disappear.
>
> Current Docker entrypoint is having launch command set to...
>
> exec gunicorn ... --access-logfile - run_pgadmin:app
>
> …with some parameters easily configurable via env vars.
>
> My proposal is to also make --access-logfile configurable, like:
>
> --access-logfile ${GUNICORN_ACCESS_LOGFILE:--}
>
> This preserves 100% backward compability and allows users like us to set
> GUNICORN_ACCESS_LOGFILE=None or another file or stdout of particular PID.
>
> --
> Seweryn Zeman
> CTO, Jazzy Innovations
>
--
Thanks and Regards,
Aditya Toshniwal
Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: pgAdmin Docker gunicorn configurable --access-logfile
In-Reply-To: <CAM9w-_=4zNuRGbOwy8jRYXWjY5ahHN+v_4zWuotHEGwxdN-=ZA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox