From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
Subject: | Re: pgAdmin4 Server does not create SQLite tables |
Date: | 2016-10-11 05:03:03 |
Message-ID: | 92351105-ae53-5894-1b01-47576bf54e5a@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On 10/10/2016 09:00 PM, Dave Page wrote:
> What is complicating matters here is that we need quite different
> configs for desktop vs. server mode, and it's hard to get that right.
> Another example, besides the paths; Devrim is configuring the security
> keys with default values in config_local.py. That's fine for desktop
> mode, but in server mode we want to explicitly force the user to create
> them, to ensure they are unique for the installation. On reflection,
> maybe I can push those into the sqlite database and have setup.py
> generate random keys in all cases.
Well, the other thing I *think* Devrim was trying to do is make
installation of pgadmin-web independent of Apache, which would allow
someone to install it under, say, nginx or uWSGI. However, in practice
that means the user needs to take a bunch of manual steps.
One thing which would improve this is to have setup.py take an optional
--directory argument.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2016-10-11 05:50:47 | Re: pgAdmin4 Server does not create SQLite tables |
Previous Message | Dave Page | 2016-10-11 04:00:02 | Re: pgAdmin4 Server does not create SQLite tables |