MIME-Version: 1.0
In-Reply-To: <b458454b-e147-2caa-f22a-326c261085ce@berkus.org>
References: <b458454b-e147-2caa-f22a-326c261085ce@berkus.org>
From: Dave Page <dpage@pgadmin.org>
Date: Thu, 12 Jan 2017 09:25:57 +0530
Message-ID: 
 <CA+OCxoyE0M1zmw+AxQqLB2FffR8i1rkLeztcTrd2yUNQEA73nw@mail.gmail.com>
Subject: Re: Building server without Apache
To: Josh Berkus <josh@berkus.org>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgadmin-hackers-owner@postgresql.org

On Thu, Jan 12, 2017 at 7:42 AM, Josh Berkus <josh@berkus.org> wrote:
> Pgadmin gurus:
>
> I'm trying to create a canonical container image for pgAdmin4 Server.
> However, using Apache is kind of heavyweight for a container.  Has
> anyone run pgAdmin4 against something lighter weight?

If memory serves, the reason why we recommend Apache is that at the
time I last tested, it was the only one of Apache, Lighttpd and Nginx
which would support single-process, multi-thread WSGI apps.

Having a single process is essential, due to the global connection
manager used by pgAdmin - it's the only way we can guarantee affinity
between the user session and the database session. If you can make
that work with servers other than Apache (someone recently suggested
Gunicorn might be able to help), then I'd love to hear about it. There
are no other special requirements of pgAdmin, so really that's all
that stands in your way.

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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers