public inbox for [email protected]  

help / color / mirror / Atom feed

pgAdmin Docker gunicorn configurable --access-logfile
2+ messages / 2 participants
[nested] [flat]

* pgAdmin Docker gunicorn configurable --access-logfile
@ 2019-11-18 11:29 Seweryn Zeman <[email protected]>
  2019-11-18 12:05 ` Re: pgAdmin Docker gunicorn configurable --access-logfile Aditya Toshniwal <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Seweryn Zeman @ 2019-11-18 11:29 UTC (permalink / raw)
  To: [email protected]

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


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: pgAdmin Docker gunicorn configurable --access-logfile
  2019-11-18 11:29 pgAdmin Docker gunicorn configurable --access-logfile Seweryn Zeman <[email protected]>
@ 2019-11-18 12:05 ` Aditya Toshniwal <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Aditya Toshniwal @ 2019-11-18 12:05 UTC (permalink / raw)
  To: Seweryn Zeman <[email protected]>; +Cc: pgadmin-hackers <[email protected]>

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"


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2019-11-18 12:05 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-11-18 11:29 pgAdmin Docker gunicorn configurable --access-logfile Seweryn Zeman <[email protected]>
2019-11-18 12:05 ` Aditya Toshniwal <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox