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 1hdzyg-0001yw-GU for pgadmin-hackers@arkaria.postgresql.org; Thu, 20 Jun 2019 16:31: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 1hdzyf-00081x-5U for pgadmin-hackers@arkaria.postgresql.org; Thu, 20 Jun 2019 16:31:57 +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 1hdzye-00081q-SD for pgadmin-hackers@lists.postgresql.org; Thu, 20 Jun 2019 16:31:56 +0000 Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdzyc-0000XR-5c for pgadmin-hackers@lists.postgresql.org; Thu, 20 Jun 2019 16:31:56 +0000 Received: by mail-wm1-x341.google.com with SMTP id g135so3695115wme.4 for ; Thu, 20 Jun 2019 09:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=uyEiQQOyH3fOXrCh4N1P0mtHMW+N1QaNxehfAtRCllA=; b=u+VgzR1seYQ6j0hGOYlKDzFBBqZgL97P+/2sWyHlFTnaCDwCOW1ipo2YVY/YIlUU9b GuaYtnwZSfmhZiVOy7FiAZMAEJJA1aOpDAROHPyjD1LQpF4bYgoEe3I61kfFEThIvsT1 ZtpkwNccR7WAjLKvz/uPGM6YCrwFqM7nnX+K+7j+CJ7Klm0gkpoQRK9Rp49sXbYmFdor Frf0diOsEZqO4ZXdR5XTVaI1P1C86lRPAg+D2jZ1DZAIoRzqDqDcT8sKEjWEVRCwzkkm U+AWtq4KppVsq8d8AH/Qm94kH51Bi8kxGRIc0mI6vh8259thSegYZuEo0shIrJxH26zW l75w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=uyEiQQOyH3fOXrCh4N1P0mtHMW+N1QaNxehfAtRCllA=; b=rSG9Dc5sKvhOIAyR0AwxtRbHDs2ek+Xy0QO8uFT5/aMyHHyQajrXigLh25zGi+aSuB QhjNIuHEZTrpDqIuzMfRKhmsxLubUq+hsXRDc7IfBcMuh81bK6LEK36eCImHGrBrKaYp UKL5xaswJhKxRU3I9+HjkOfUX4byUKbOfAdZNHG8tE2hXVasUf8YOPUYRvrSY2MI0rT6 tYekhWVcGOymeJpwct0pl5V1fGOoppiebzHIgYZ2qsLVdEHdveWKrnI32IxENU6IUXnA ElTYk8PVQ+wUxMSc0QQ7valEYM+MicxifH5ZWMyiKB25ECqyDPsKJs3jLfssqkw9Qb1s zSZA== X-Gm-Message-State: APjAAAVtiv8pZCcIBL1MVe1jKPCv8rmLsdGHDGI0TgF9KfyeWub88ui0 0yVlc4W8MOihjkW8TOy03FHgi1SnII1rGMfW6hM1U1TW1nA= X-Google-Smtp-Source: APXvYqw775n88NvjpvYDdvFA4ihf7hK4RYrNYBnwgByF54uG8d/8g0agoDZzGHoJndveK5V91A+zwG+i9whocoyPXgE= X-Received: by 2002:a7b:c7d7:: with SMTP id z23mr359002wmk.46.1561048312490; Thu, 20 Jun 2019 09:31:52 -0700 (PDT) MIME-Version: 1.0 From: Andrew Coleman Date: Thu, 20 Jun 2019 12:31:40 -0400 Message-ID: Subject: change to Docker entrypoint.sh To: pgadmin-hackers@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000024af04058bc3e287" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000024af04058bc3e287 Content-Type: text/plain; charset="UTF-8" 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. The code is here: https://github.com/penguincoder/pgadmin4/commit/0865400385ac0d03bf69d183e8cd9aaec6dcf318 Is this something that anyone is interested in? Does it meet your coding standards? What do I do next? I would love to move back to the "official" pgadmin container. Thanks for your time, Andrew --00000000000024af04058bc3e287 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All!

I am new to this, so= I apologize beforehand if it's not entirely kosher, but I have a propo= sed change to the Dockerfile entrypoint.sh to allow for configurable server= s.json filename path.

The reasoning behind this is= that I have a Kubernetes deployment of pgadmin where I build a ConfigMap s= ort 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 environm= ent variable in my custom Helm chart for my deployment.