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 1iWfED-0000CS-Rj for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Nov 2019 11:29:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iWfEA-0006ny-Uo for pgadmin-hackers@arkaria.postgresql.org; Mon, 18 Nov 2019 11:29:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iWfEA-0006nr-JN for pgadmin-hackers@lists.postgresql.org; Mon, 18 Nov 2019 11:29:54 +0000 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iWfE3-0000iG-AC for pgadmin-hackers@lists.postgresql.org; Mon, 18 Nov 2019 11:29:53 +0000 Received: by mail-lj1-x232.google.com with SMTP id d5so18491161ljl.4 for ; Mon, 18 Nov 2019 03:29:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jazzy.pro; s=google; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=MDvjkDwbbUhivr1D9gXUR4D2C+8w6kNry3LvDzFdtUs=; b=aFzk19v5hXlwuIv7Z76wl2PX8DR2OhIxLILMgJX63+UyJNVoBw2l3iRoVDtzGQoDLA gIpOXeMmetQ7CFwxf2CQCfsUPNGqfo+cP6AmEoonJOI0Lqf5bys0eBT0GfgeU6+kwXuC wyC35+f8L+7TYToy1vNyW27Pr0aEo5FqTkhcc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=MDvjkDwbbUhivr1D9gXUR4D2C+8w6kNry3LvDzFdtUs=; b=rj16oCFQPMh2ptfp1S2IuiXB61geq9OL4AvNq3Ixnv/kQs3xrTgk3qWp4tQdESP4LF Yxo4T44l0wy3/w8+f66s6YsSzc8RSF206bdP+mfU0YhmtXdU7Gj9nAutQZee/ZpHjpI3 08LMbE9oP4Ym5C0isl0bMxtsY1bGdUcPKAFBvitkjmSvRm0FKq4U9Mu6De4pWhb7BqNh NrN2d2djsHcJQ4m/P+RJg9iJ8qVdRem0qh3KRP8NqJCaQQBTpCdWYYvnPhSzhCoeCKIf H9bfXVb/nILPxBpvA9E55wsAne/8IkWQ91HH2POUWCaHcTSxTrObiFi0UzSqjzbPOm6K C0Tw== X-Gm-Message-State: APjAAAVGP3xd2qE2UEsMnIBf2k51ty1KuL8YGdyQTH51e/7n079Bk1nB 8dzAtq2toZT6YRnzICpo70H21gobxOK+Lg== X-Google-Smtp-Source: APXvYqz6AkvdfItX0X5DYLbkgHwEPBdn4s5BcvH9IOKNGznPPlTzGBoad/9MseBvvZ1xm/lT8aaS+Q== X-Received: by 2002:a2e:9e8f:: with SMTP id f15mr20867568ljk.9.1574076585023; Mon, 18 Nov 2019 03:29:45 -0800 (PST) Received: from [192.168.1.20] ([185.53.155.78]) by smtp.gmail.com with ESMTPSA id s28sm8963389lfp.92.2019.11.18.03.29.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Nov 2019 03:29:44 -0800 (PST) Date: Mon, 18 Nov 2019 12:29:32 +0100 From: Seweryn Zeman To: pgadmin-hackers@lists.postgresql.org Message-ID: <26c74197-524c-432b-b19b-2b3ca36151bd@Spark> In-Reply-To: References: Subject: pgAdmin Docker gunicorn configurable --access-logfile X-Readdle-Message-ID: 26c74197-524c-432b-b19b-2b3ca36151bd@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5dd280a7_1381823a_333" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --5dd280a7_1381823a_333 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, me and my company is working with pgAdmin since we decided to use pgS= ql =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 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=5Fpgadmin:app =E2=80=A6with some parameters easily configurable via env vars. My proposal is to also make --access-logfile configurable, like: --access-logfile =24=7BGUNICORN=5FACCESS=5FLOG=46ILE:--=7D This preserves 100% backward compability and allows users like us to set=C2= =A0GUNICORN=5FACCESS=5FLOG=46ILE=3DNone=C2=A0or another file or stdout of= particular PID. -- Seweryn Zeman CTO, Jazzy Innovations --5dd280a7_1381823a_333 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi, me and my company is working with pgAdmin since we decided to use pg= Sql =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 ca= n see lots of access logs for HTTP and WS which are very irrelevant to us= . This makes important logs to disappear.

<= /div>
Current Docker= entrypoint is having launch command set to...

exec gunicorn ... --access-logfile - run=5Fpgadmin:app

=E2=80=A6with some parameters easily = configurable via env vars.
<= font style=3D=22font-size: 13px;=22>
<= font style=3D=22font-size: 13px;=22>My proposal is to also make --access-= logfile configurable, like:
<= font style=3D=22font-size: 13px;=22>
--access-logfile =24=7BGUNICORN=5FACCE= SS=5FLOG=46ILE:--=7D

This= preserves 100% backward compability and allows users like us to set&=231= 60;GUNICORN=5FACCESS=5FL= OG=46ILE=3DNone&= =23160;or another file or stdout of particular PID.

--
Seweryn Zeman
CTO, Jazzy Innovations
--5dd280a7_1381823a_333--