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 1heEqR-0004Ok-FK for pgadmin-hackers@arkaria.postgresql.org; Fri, 21 Jun 2019 08:24:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1heEqQ-0001dk-9y for pgadmin-hackers@arkaria.postgresql.org; Fri, 21 Jun 2019 08:24:26 +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 1heEqP-0001da-Md for pgadmin-hackers@lists.postgresql.org; Fri, 21 Jun 2019 08:24:26 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1heEqM-0000Fg-FH for pgadmin-hackers@lists.postgresql.org; Fri, 21 Jun 2019 08:24:24 +0000 Received: by mail-wm1-x344.google.com with SMTP id c66so5517642wmf.0 for ; Fri, 21 Jun 2019 01:24:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IEfCdx2UsEYj18VgGS/JynoS3NLi82mbvDNNNiIgdgQ=; b=ZMBzK3z4lYEj7RyChe5uShRCqrkIGf/ZOvspd9yVr2/mgm7m2febJlN4hVFQtx40Bq mUE5qKluwCHX1Tg8owA9lO7WzvQQBrBvKvyIncy3HsyHCSLo+fpYPMs7hiJqTJF+iwRK cvb2NFA2MN3VAY+bN1/ndVSk+97kQkCSJWBSTls4n4GyybLFQ7zq9Q2+5ts10Qwvp96X emNHNmDNXLZ88RP9ILJPckyraJcRgyBQydgwJoFWBnrxu9vNudGtEB7SIuolADvCS4v0 AhdBK58tBXQSjbZWeqTez+R3XESb7PoRt+fUAl1s1Su+wDrCUDmtNmYkR0Ax+ZDCxSCq tnhA== 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=IEfCdx2UsEYj18VgGS/JynoS3NLi82mbvDNNNiIgdgQ=; b=s2GkZUHDcaeAKHuiUHw/pT3EElCgUQClvnKXFjSjCdd85v0A8DPw+EEpmLYhcozAkU Jfzc6H9DXenHswo6Nob4k87QOcBLYqvEVRRD2zTDqwxR69G8OL1Hta9EC3jd5d/sqt9h JCkIEXuIyp0i5EPgBCIDfO15r1zOZMyngHg2pw2YZSIuJspZHMHplWNrRYtZraL7A/h9 WJOHhWfpt4mNx9VzHgT4R06sj++7M2YBwnL9s/BZA0N0FCblBF5yBpmejU1AJaqiQYoA rHYTLJU2kLDwl1AyPhF6ld2MXBLvy1pke0WNek4LMRPePAqX3t5ooa1GSJjSLIGMm01w UgvQ== X-Gm-Message-State: APjAAAWhQogy5z2h/P5b9nlEziFJ6H6ONfS3aI7MNdmPWv7xYGgXgiUe RSn90O5QNgV+duPuT1ruy0Qy8CKL527yW0BSJq1/3w== X-Google-Smtp-Source: APXvYqz18kWz+3DTmf3JyfowMgBoD4EoXxyQIByOxr07crdAKQ8gBx6cOm2gO1KqyrDf+RzX3W2EghHqS2caUS6g4nM= X-Received: by 2002:a1c:eb0a:: with SMTP id j10mr3286383wmh.1.1561105460620; Fri, 21 Jun 2019 01:24:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Fri, 21 Jun 2019 09:24:08 +0100 Message-ID: Subject: Re: change to Docker entrypoint.sh To: Andrew Coleman Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000700502058bd13090" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000700502058bd13090 Content-Type: text/plain; charset="UTF-8" Hi On Thu, Jun 20, 2019 at 5:31 PM Andrew Coleman wrote: > Hi All! > > I am new to this, so I apologize beforehand if it's not entirely kosher, > but I have a proposed change to the Dockerfile entrypoint.sh to allow for > configurable servers.json filename path. > > The reasoning behind this is that I have a Kubernetes deployment of > pgadmin where I build a ConfigMap sort of dynamically. I can make the file > appear in /pgadmin4, but it removes the contents of the directory for me > (helpful!). Instead, I put it into a separate directory and set a new > environment variable that defaults to the old pathname > (backwards-compatible!) but allows me to set a custom environment variable > in my custom Helm chart for my deployment. > pgAdmin removes the content of the directory? I'm not sure how it would do that - it doesn't delete anything like that. > > The code is here: > > https://github.com/penguincoder/pgadmin4/commit/0865400385ac0d03bf69d183e8cd9aaec6dcf318 > > Is this something that anyone is interested in? > Sure. > Does it meet your coding standards? > Looks fine to me. > What do I do next? > > I would love to move back to the "official" pgadmin container. > Please raise a feature request at https://redmine.postgresql.org/projects/pgadmin4/issues/new and attach the patch (just use git diff against a checkout of the master branch). You can send the patch here, but we need the feature request in the tracker anyway, so it's probably easier to attach it there. Thanks! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --000000000000700502058bd13090 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Thu, Jun 20, 2019 at 5:31 PM Andrew = Coleman <penguincoder@gmail.co= m> wrote:
Hi All!

I am new to this, s= o I apologize beforehand if it's not entirely kosher, but I have a prop= osed change to the Dockerfile entrypoint.sh to allow for configurable serve= rs.json filename path.

The reasoning behind this i= s that I have a Kubernetes deployment of pgadmin where I build a ConfigMap = sort of dynamically. I can make the file appear in /pgadmin4, but it remove= s the contents of the directory for me (helpful!). Instead, I put it into a= separate directory and set a new environment variable that defaults to the= old pathname (backwards-compatible!) but allows me to set a custom environ= ment variable in my custom Helm chart for my deployment.

pgAdmin removes the content of the directory? I&#= 39;m not sure how it would do that - it doesn't delete anything like th= at.
=C2=A0

The code is here:

=
Is this something that anyone is interested in?

Sure.
=C2=A0
Does it meet your coding sta= ndards?

Looks fine to me.
=C2=A0
What do I do next?

I = would love to move back to the "official" pgadmin container.

Please raise a feature request at= =C2=A0https://redmine.postgresql.org/projects/pgadmin4/issues/new=C2=A0and= attach the patch (just use git diff against a checkout of the master branc= h). You can send the patch here, but=C2=A0=C2=A0we need the feature request= in the tracker anyway, so it's probably easier to attach it there.

Thanks!


-= -
Dave Page
Blog: http://pgsnake.blogspot.= com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The = Enterprise PostgreSQL Company
--000000000000700502058bd13090--