Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d1U0I-0006aS-KE for pgadmin-hackers@arkaria.postgresql.org; Fri, 21 Apr 2017 08:33:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d1U0H-0001sf-PR for pgadmin-hackers@arkaria.postgresql.org; Fri, 21 Apr 2017 08:33:21 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d1U0H-0001sV-A0 for pgadmin-hackers@postgresql.org; Fri, 21 Apr 2017 08:33:21 +0000 Received: from mail-io0-x22b.google.com ([2607:f8b0:4001:c06::22b]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d1U0C-0006Y5-Bk for pgadmin-hackers@postgresql.org; Fri, 21 Apr 2017 08:33:20 +0000 Received: by mail-io0-x22b.google.com with SMTP id r16so105036073ioi.2 for ; Fri, 21 Apr 2017 01:33:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0kaJiFMRKE/EHV/0A7N0WF06UxVEaZFtwPyAxCsz5zA=; b=nwLDDacpG6NPsCj8i7D3nj85GGskneB2kZxleGG0bggnatztUtg2JYaVjzIMEh/qqV Bd8kNrbgmmLYWmZA2bw9DK8Julvc5jxgZqIe47JzhrteLX4e/0uzXgINWPfRzzghyBeS Y24tsvx27gvo9CxqJ2XB8+MIVWn4EWzUnmDruzOJNrDrbh9Yah67ZnE7xJu1dK2vRdhO f87tw1InkQfT5fvMeeiHiP1erz+5Ffrdxa20/9ZLRNXv7CVBb6ACOfG6a3TlV+645B94 pMErTFLizxHBLTGEE828B6nTKKagnb4RNn7zXjhk9tNrMpRvpw10ZbLS0VVBOc1s3KDn Xd2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0kaJiFMRKE/EHV/0A7N0WF06UxVEaZFtwPyAxCsz5zA=; b=Q2Q6QTUF9PrI8HQ60GCqyUEZy/vRy7PkAa9VGAdvK1jxZ+oZAXiA7fznKBIJG7w23y B+cW24nPNx8TT/jMKkvhF+H5PXQnq4Bz8iEB/QeKHpqKnfyPBSsNWCeRbEjhU9aELwW0 NLwX+krtNslHq+6awJRZBzuTNbIICWyiaa+3dlzAERhyShWBHJ4s+LEPg0oehhOW2e6y xZNUf6Vq3PFnePO1h5JuMS9ve0evo/JGvt6KlF2rT2ZR/DWP3UxUHFma32ssxX53LUkj Z9lfSD+3cwAp0OP1LLqqxrtxPr011LzWjwC4Rw6i1y31/hXfY9OEr8O8rqxoEqN5DeRq htVg== X-Gm-Message-State: AN3rC/51wPytL/R/tycRCV85x32j7bHQ1q1b46QIKTpmZHDn1dhNF8wx 0C+ole6PdOk2mi9LPPv5ER1KFqvYXPHxOEY= X-Received: by 10.107.44.71 with SMTP id s68mr15244282ios.126.1492763591890; Fri, 21 Apr 2017 01:33:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.174.167 with HTTP; Fri, 21 Apr 2017 01:33:11 -0700 (PDT) In-Reply-To: <8ca2ba41-b46f-a89e-6b1b-4b7277348685@berkus.org> References: <8ca2ba41-b46f-a89e-6b1b-4b7277348685@berkus.org> From: Dave Page Date: Fri, 21 Apr 2017 09:33:11 +0100 Message-ID: Subject: Re: Some questions about configuration and the pgadmin4-v1-web package To: Josh Berkus Cc: pgadmin-hackers , =?UTF-8?B?RGV2cmltIEfDnE5Ew5xa?= Content-Type: multipart/alternative; boundary=001a11399c90a0eb4e054da91be3 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a11399c90a0eb4e054da91be3 Content-Type: text/plain; charset=UTF-8 On Thu, Apr 20, 2017 at 9:50 PM, Josh Berkus wrote: > pgAdmin team, Devrim: > > If I install the pgadmin4-v1-web package from Yum, it's a bit unclear on > what actual configuration needs to be done after that. Things I know > need to be done: > > * running setup.py > * copying the httpd/conf.d/pgadmin4-web.conf.example file to a .conf file > > Things I don't know if they need to be done: > > 1. creating data and log directories and assigning permissions on them > 2. changing the permissions on the sqlite db > 3. creating a config_local.py file and setting the five settings in it > > Can you clarify? I'm working on a container, and I'll also be happy to > contribute a doc if you can clarify via email. Thanks. > I don't know how much of that work is done by the RPMs, so Devrim will need to chime in on this one. I suspect you will need to do 1-3 though. For a source/pip installation (would a pure Python installation be a better basis for a container?), the docs at https://www.pgadmin.org/docs4/1.x/server_deployment.html should cover everything (patches to improve are always welcome of course). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a11399c90a0eb4e054da91be3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Apr 20, 2017 at 9:50 PM, Josh Berkus <josh@berkus.org> wrote:
pgAdmin te= am, Devrim:

If I install the pgadmin4-v1-web package from Yum, it's a bit unclear o= n
what actual configuration needs to be done after that. Things I know
need to be done:

* running setup.py
* copying the httpd/conf.d/pgadmin4-web.conf.example file to a .conf f= ile

Things I don't know if they need to be done:

1. creating data and log directories and assigning permissions on them
2. changing the permissions on the sqlite db
3. creating a config_local.py file and setting the five settings in it

Can you clarify?=C2=A0 I'm working on a container, and I'll also be= happy to
contribute a doc if you can clarify via email.=C2=A0 Thanks.

I don't know how much of that work is done by the= RPMs, so Devrim will need to chime in on this one. I suspect you will need= to do 1-3 though.

For a source/pip installation (= would a pure Python installation be a better basis for a container?), the d= ocs at=C2=A0https://www.pgadmin.org/docs4/1.x/server_deployment.html should c= over everything (patches to improve are always welcome of course).

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

Ent= erpriseDB UK: htt= p://www.enterprisedb.com
The Enterprise PostgreSQL Company
--001a11399c90a0eb4e054da91be3--