Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iWfnE-0001gR-Jm for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Nov 2019 12:06:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iWfnD-00053V-Bz for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Nov 2019 12:06:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iWfnC-00050N-Te for pgadmin-hackers@lists.postgresql.org; Mon, 18 Nov 2019 12:06:07 +0000 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iWfn5-0006m8-NZ for pgadmin-hackers@lists.postgresql.org; Mon, 18 Nov 2019 12:06:06 +0000 Received: by mail-ot1-x342.google.com with SMTP id f10so14277565oto.3 for ; Mon, 18 Nov 2019 04:05:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ig9tIf2mxy+AU1KFh3cLBogrZqstuAmp/Ht/CiRVwjM=; b=K9sv+3FruyJ2Hgf2l0rkz/7niotlAb7OrELNihhwNVHsWUB9AGyWk2QccYKdjtik5C +A+UJKt44IHjgIpWLa2IZcJxUKP1+jJBJmaq2nKjzgzCgLijP9aGKioWPHkFoZ334vsT TXY9v1z20xt02trPN3Xrp/1V/Hw7DKbjKaBJT1Tli+x5dZoX9VZD+2osOoflaNhc2fX6 D+CD1ttEbdBbLKJQ9PfFQkOKiCk2xm/Au6olWEwcbcpK0VTQeKSFdh4ZUrYjkfL5AIgN AYpSWOToFGKEirmhUPf+Ner8lsdmkrswINKw7AvHwa7BLbQfcwuoRvBQcfFyA4pw/kNr 85oQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ig9tIf2mxy+AU1KFh3cLBogrZqstuAmp/Ht/CiRVwjM=; b=IJ0BNsc7WmsYNd37/N8g47yr5hEWA3YGaAhXknOOuHwP/fxdtc4WU+ho4l6CsKbCuW bPd6jOmoz+QMvYveb02G5sOZAlv0hRuxl8zsOpRRGGm2o4vRaxFpWyimdgvVatugcPnF gXAaCa0WednmMMyK4zf6Kn6J0ci3frKiq/EZo4HtGgmT43di18rx1C+n0Esd5chYkuMK FheGF1IxVX45ptqnsWWYMsLADSegcKFIlvOlMRi+JlNtDOS70yzkALgDz9+fVHD6dWHJ kaseW6Ccx5p2oLde6wg+K0X5+J6g0b6F2nBP4SqbpqfjAey7iJ58WmWxjHEzhrApHaqM A+4A== X-Gm-Message-State: APjAAAWvhWea82efcsiMKPjj6JTljyKeY84O0rvU52UOJKl3sXAtwwVq l3J0dGSEiuOSnpe1e3Uc1mMhjFoRhSSO1QddTEeXzbGq3zHbPfYouYLNyJdYv+t3okf22kcyMKG XC/OLS8llGUBlVkBAUrVgWmtVrnBz+qxxZNVwGmC2ohffjNKBaeyQvqxceoUBwtayRRlbpzZ5Bk 6crqTjvtHWdEiGCoSIS7xtpn0ZbgpeNwbb6s7C02+COkwKnvKSUyJDq8QN7fie/qSwK3Y= X-Google-Smtp-Source: APXvYqxHyLSvvHjHNo/fzFcA30QxSg9pybAk4VERPh4RPRCKA51gR1Gq4/sZu0Wn1Twy73uGzJB8jSSGMhgpnKhWp0g= X-Received: by 2002:a9d:5d1a:: with SMTP id b26mr22606103oti.139.1574078757531; Mon, 18 Nov 2019 04:05:57 -0800 (PST) MIME-Version: 1.0 References: <26c74197-524c-432b-b19b-2b3ca36151bd@Spark> In-Reply-To: <26c74197-524c-432b-b19b-2b3ca36151bd@Spark> From: Aditya Toshniwal Date: Mon, 18 Nov 2019 17:35:21 +0530 Message-ID: Subject: Re: pgAdmin Docker gunicorn configurable --access-logfile To: Seweryn Zeman Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000310a6a05979dc591" X-CLOUD-SEC-AV-Info: edb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000310a6a05979dc591 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 wrote: > Hi, me and my company is working with pgAdmin since we decided to use > pgSql =E2=80=93 mostly for development with containers. In this case Dock= er. While > starting a docker-compose in dev mode with pgAdmin in stack we can see lo= ts > of access logs for HTTP and WS which are very irrelevant to us. This make= s > important logs to disappear. > > Current Docker entrypoint is having launch command set to... > > exec gunicorn ... --access-logfile - run_pgadmin:app > > =E2=80=A6with 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=3DNone or another file or stdout of particular PI= D. > > -- > Seweryn Zeman > CTO, Jazzy Innovations > --=20 Thanks and Regards, Aditya Toshniwal Sr. Software Engineer | EnterpriseDB India | Pune "Don't Complain about Heat, Plant a TREE" --000000000000310a6a05979dc591 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Seweryn,

Kindly=C2=A0raise a feature request her= e -=C2=A0https://redmine.post= gresql.org/projects/pgadmin4/issues/new

On Mon, Nov 18, 2019 at 4:= 59 PM Seweryn Zeman <seweryn.= zeman@jazzy.pro> wrote:
Hi, me and = my company is working with pgAdmin since we decided to use pgSql =E2=80=93 = 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 acce= ss logs for HTTP and WS which are very irrelevant to us. This makes importa= nt logs to disappear.

Current Docker entrypoint = is having launch command set to...

exec gunicorn ... = --access-logf= ile - = run_pgadmin:app

=E2=80=A6with some p= arameters easily configurable via env vars.
My proposal is to al= so make --access-logfile configurable, like:
--access-logfile ${GUNICORN_ACCESS_LOGFILE:= --}

This preserves 100% backward compability and allows= users like us to set=C2=A0GUNICORN_ACCESS_LOGFILE=3DNone=C2=A0or another= file or stdout of particular PID.

--
Seweryn Zeman
CTO, Jazzy Innovations


--
Thanks and Regards,
Aditya Toshniwal
Sr. Software Engineer |=C2=A0EnterpriseDB In= dia |=C2=A0Pune
"Don't Complain about Heat, Plant a TREE"
=
--000000000000310a6a05979dc591--