Message-ID: <76354c477f2636a93d891528b66c5b8c6d6b1db5.camel@ageofdream.com>
Subject: Questions about the Debian Package version of pgAdmin
From: Nick <lists2@ageofdream.com>
To: pgsql-general@lists.postgresql.org
Date: Sun, 05 Jan 2025 19:27:15 -0500
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4-2 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/76354c477f2636a93d891528b66c5b8c6d6b1db5.camel%40ageofdream.com>
Precedence: bulk


I sent this to the PgAdmin list but didn't get any replies. Not sure
how many people are on that list, but since these questions are general
enough, I figure someone on the main list will know:

I'm using the apt repository version for Debian 12 (Bookworm). I'm also
using Ansible to manage the server, and I have some questions about the
pgAdmin Debian package version.

1. If we're using the pgAdmin DEB repo, will `apt-update` always update
pgAdmin to the latest major version? ie. Will we be doing an upgrade
every four weeks?

2. Should `sudo /usr/pgadmin4/bin/setup-web.sh` be run every time `apt-
update` runs, or only once?

3. Since the package is also installing Apache for us and configuring
it, is there a safe way for us to modify the Apache config without
breaking updates?

We'd like to enable TLS for Apache, but in a way that doesn't break
anything each time the setup playbook runs and updates PgAdmin.

Thanks,
Nick