public inbox for [email protected]
help / color / mirror / Atom feedPackagers: Handling upgrade checks
6+ messages / 4 participants
[nested] [flat]
* Packagers: Handling upgrade checks
@ 2019-01-02 13:13 Dave Page <[email protected]>
2019-01-03 09:59 ` Re: Packagers: Handling upgrade checks Christoph Berg <[email protected]>
2019-02-05 12:27 ` Re: Packagers: Handling upgrade checks Sandeep Thakkar <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Dave Page @ 2019-01-02 13:13 UTC (permalink / raw)
To: Devrim GÜNDÜZ <[email protected]>; Christoph Berg <[email protected]>; Sandeep Thakkar <[email protected]>; +Cc: pgadmin-hackers
Packagers,
As you probably know, pgAdmin 4 checks for updates upon startup, and
if a newer version is available, directs the user to www.pgadmin.org
to download it.
The is a problem if your pgAdmin came with a PostgreSQL installer (as
you can't download them from our website), and potentially mildly
annoying if you're a .deb or .rpm user.
There are a couple of ways to optimise the experience for users here
(one of which I just committed). I'll leave it up to each of you to
choose what you want to do (Sandeep, I would suggest that the EDB
installers use method 2).
Method 1: Simply disable the upgrade check, and leave that to the
operating systems update tools. To do this, create (or edit) a
config_distro.py file that is installed alongside the config.py file
from the pgAdmin source and include the line;
UPGRADE_CHECK_ENABLED = False
Method 2: For well known and trusted distributions we can support a
custom check for your distribution. This involves 2 parts:
1) Let me know that you want a custom check, and I'll setup access for
you to manage the version data on the pgAdmin website. We'll agree on
a custom key for that data within the JSON file the website hosts.
2) Create (or edit) a config_distro.py file that is installed
alongside the config.py file from the pgAdmin source and include the
line;
UPGRADE_CHECK_KEY = '<your key>'
With this method, a different section of the JSON datafile will be
checked by your distribution of pgAdmin, thus allowing you to control
both when it tells users a new version is available, and the URL to
which they are directed.
Thanks!
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Packagers: Handling upgrade checks
2019-01-02 13:13 Packagers: Handling upgrade checks Dave Page <[email protected]>
@ 2019-01-03 09:59 ` Christoph Berg <[email protected]>
2019-01-03 11:00 ` Re: Packagers: Handling upgrade checks Devrim Gündüz <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Christoph Berg @ 2019-01-03 09:59 UTC (permalink / raw)
To: Dave Page <[email protected]>; +Cc: Devrim GÜNDÜZ <[email protected]>; Sandeep Thakkar <[email protected]>; pgadmin-hackers
Re: Dave Page 2019-01-02 <CA+OCxowHgi-ALNp3w+B_GYM+hJn_2oe+PzgRWY1Ld5PHQ7Yggg@mail.gmail.com>
> As you probably know, pgAdmin 4 checks for updates upon startup, and
> if a newer version is available, directs the user to www.pgadmin.org
> to download it.
>
> UPGRADE_CHECK_ENABLED = False
For Debian, I'll use this method. Programs "calling home" is actually
considered to be a privacy breach.
Christoph
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Packagers: Handling upgrade checks
2019-01-02 13:13 Packagers: Handling upgrade checks Dave Page <[email protected]>
2019-01-03 09:59 ` Re: Packagers: Handling upgrade checks Christoph Berg <[email protected]>
@ 2019-01-03 11:00 ` Devrim Gündüz <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Devrim Gündüz @ 2019-01-03 11:00 UTC (permalink / raw)
To: Christoph Berg <[email protected]>; Dave Page <[email protected]>; +Cc: Sandeep Thakkar <[email protected]>; pgadmin-hackers
Hi,
On Thu, 2019-01-03 at 10:59 +0100, Christoph Berg wrote:
> > UPGRADE_CHECK_ENABLED = False
>
> For Debian, I'll use this method. Programs "calling home" is actually
> considered to be a privacy breach.
Same here for the RPMs. That would also help if the RPMs are not released on
time :-)
Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Packagers: Handling upgrade checks
2019-01-02 13:13 Packagers: Handling upgrade checks Dave Page <[email protected]>
@ 2019-02-05 12:27 ` Sandeep Thakkar <[email protected]>
2019-02-05 13:36 ` Re: Packagers: Handling upgrade checks Dave Page <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Sandeep Thakkar @ 2019-02-05 12:27 UTC (permalink / raw)
To: Dave Page <[email protected]>; +Cc: Srinu Perabattula <[email protected]>; pgadmin-hackers
Hi Dave,
On Wed, Jan 2, 2019 at 6:44 PM Dave Page <[email protected]> wrote:
> Packagers,
>
> As you probably know, pgAdmin 4 checks for updates upon startup, and
> if a newer version is available, directs the user to www.pgadmin.org
> to download it.
>
> The is a problem if your pgAdmin came with a PostgreSQL installer (as
> you can't download them from our website), and potentially mildly
> annoying if you're a .deb or .rpm user.
>
> There are a couple of ways to optimise the experience for users here
> (one of which I just committed). I'll leave it up to each of you to
> choose what you want to do (Sandeep, I would suggest that the EDB
> installers use method 2).
>
> Method 1: Simply disable the upgrade check, and leave that to the
> operating systems update tools. To do this, create (or edit) a
> config_distro.py file that is installed alongside the config.py file
> from the pgAdmin source and include the line;
>
> UPGRADE_CHECK_ENABLED = False
>
> Method 2: For well known and trusted distributions we can support a
> custom check for your distribution. This involves 2 parts:
>
> 1) Let me know that you want a custom check, and I'll setup access for
> you to manage the version data on the pgAdmin website. We'll agree on
> a custom key for that data within the JSON file the website hosts.
>
> We want that for PG and EPAS installers. Will you please share the custom
key?
> 2) Create (or edit) a config_distro.py file that is installed
> alongside the config.py file from the pgAdmin source and include the
> line;
>
> UPGRADE_CHECK_KEY = '<your key>'
>
> With this method, a different section of the JSON datafile will be
> checked by your distribution of pgAdmin, thus allowing you to control
> both when it tells users a new version is available, and the URL to
> which they are directed.
>
> Makes sense. Will include this change in the upcoming PG and EPAS updates
that bundle pgAdmin.
> Thanks!
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
Sandeep Thakkar
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Packagers: Handling upgrade checks
2019-01-02 13:13 Packagers: Handling upgrade checks Dave Page <[email protected]>
2019-02-05 12:27 ` Re: Packagers: Handling upgrade checks Sandeep Thakkar <[email protected]>
@ 2019-02-05 13:36 ` Dave Page <[email protected]>
2019-02-07 09:35 ` Re: Packagers: Handling upgrade checks Sandeep Thakkar <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Dave Page @ 2019-02-05 13:36 UTC (permalink / raw)
To: Sandeep Thakkar <[email protected]>; +Cc: Srinu Perabattula <[email protected]>; pgadmin-hackers
Hi
On Tue, Feb 5, 2019 at 12:27 PM Sandeep Thakkar
<[email protected]> wrote:
>
> Hi Dave,
>
>
> On Wed, Jan 2, 2019 at 6:44 PM Dave Page <[email protected]> wrote:
>>
>> Packagers,
>>
>> As you probably know, pgAdmin 4 checks for updates upon startup, and
>> if a newer version is available, directs the user to www.pgadmin.org
>> to download it.
>>
>> The is a problem if your pgAdmin came with a PostgreSQL installer (as
>> you can't download them from our website), and potentially mildly
>> annoying if you're a .deb or .rpm user.
>>
>> There are a couple of ways to optimise the experience for users here
>> (one of which I just committed). I'll leave it up to each of you to
>> choose what you want to do (Sandeep, I would suggest that the EDB
>> installers use method 2).
>>
>> Method 1: Simply disable the upgrade check, and leave that to the
>> operating systems update tools. To do this, create (or edit) a
>> config_distro.py file that is installed alongside the config.py file
>> from the pgAdmin source and include the line;
>>
>> UPGRADE_CHECK_ENABLED = False
>>
>> Method 2: For well known and trusted distributions we can support a
>> custom check for your distribution. This involves 2 parts:
>>
>> 1) Let me know that you want a custom check, and I'll setup access for
>> you to manage the version data on the pgAdmin website. We'll agree on
>> a custom key for that data within the JSON file the website hosts.
>>
> We want that for PG and EPAS installers. Will you please share the custom key?
edb-pgadmin4
See: https://www.pgadmin.org/versions.json (let me know if I need to
change anything for testing etc).
>>
>> 2) Create (or edit) a config_distro.py file that is installed
>> alongside the config.py file from the pgAdmin source and include the
>> line;
>>
>> UPGRADE_CHECK_KEY = '<your key>'
>>
>> With this method, a different section of the JSON datafile will be
>> checked by your distribution of pgAdmin, thus allowing you to control
>> both when it tells users a new version is available, and the URL to
>> which they are directed.
>>
> Makes sense. Will include this change in the upcoming PG and EPAS updates that bundle pgAdmin.
:-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Packagers: Handling upgrade checks
2019-01-02 13:13 Packagers: Handling upgrade checks Dave Page <[email protected]>
2019-02-05 12:27 ` Re: Packagers: Handling upgrade checks Sandeep Thakkar <[email protected]>
2019-02-05 13:36 ` Re: Packagers: Handling upgrade checks Dave Page <[email protected]>
@ 2019-02-07 09:35 ` Sandeep Thakkar <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Sandeep Thakkar @ 2019-02-07 09:35 UTC (permalink / raw)
To: Dave Page <[email protected]>; +Cc: Srinu Perabattula <[email protected]>; pgadmin-hackers
On Tue, Feb 5, 2019 at 7:06 PM Dave Page <[email protected]> wrote:
> Hi
>
> On Tue, Feb 5, 2019 at 12:27 PM Sandeep Thakkar
> <[email protected]> wrote:
> >
> > Hi Dave,
> >
> >
> > On Wed, Jan 2, 2019 at 6:44 PM Dave Page <[email protected]> wrote:
> >>
> >> Packagers,
> >>
> >> As you probably know, pgAdmin 4 checks for updates upon startup, and
> >> if a newer version is available, directs the user to www.pgadmin.org
> >> to download it.
> >>
> >> The is a problem if your pgAdmin came with a PostgreSQL installer (as
> >> you can't download them from our website), and potentially mildly
> >> annoying if you're a .deb or .rpm user.
> >>
> >> There are a couple of ways to optimise the experience for users here
> >> (one of which I just committed). I'll leave it up to each of you to
> >> choose what you want to do (Sandeep, I would suggest that the EDB
> >> installers use method 2).
> >>
> >> Method 1: Simply disable the upgrade check, and leave that to the
> >> operating systems update tools. To do this, create (or edit) a
> >> config_distro.py file that is installed alongside the config.py file
> >> from the pgAdmin source and include the line;
> >>
> >> UPGRADE_CHECK_ENABLED = False
> >>
> >> Method 2: For well known and trusted distributions we can support a
> >> custom check for your distribution. This involves 2 parts:
> >>
> >> 1) Let me know that you want a custom check, and I'll setup access for
> >> you to manage the version data on the pgAdmin website. We'll agree on
> >> a custom key for that data within the JSON file the website hosts.
> >>
> > We want that for PG and EPAS installers. Will you please share the
> custom key?
>
> edb-pgadmin4
>
> See: https://www.pgadmin.org/versions.json (let me know if I need to
> change anything for testing etc).
>
> Nice! Thank you.
> >>
> >> 2) Create (or edit) a config_distro.py file that is installed
> >> alongside the config.py file from the pgAdmin source and include the
> >> line;
> >>
> >> UPGRADE_CHECK_KEY = '<your key>'
> >>
> >> With this method, a different section of the JSON datafile will be
> >> checked by your distribution of pgAdmin, thus allowing you to control
> >> both when it tells users a new version is available, and the URL to
> >> which they are directed.
> >>
> > Makes sense. Will include this change in the upcoming PG and EPAS
> updates that bundle pgAdmin.
>
> :-)
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
Sandeep Thakkar
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2019-02-07 09:35 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-01-02 13:13 Packagers: Handling upgrade checks Dave Page <[email protected]>
2019-01-03 09:59 ` Christoph Berg <[email protected]>
2019-01-03 11:00 ` Devrim Gündüz <[email protected]>
2019-02-05 12:27 ` Sandeep Thakkar <[email protected]>
2019-02-05 13:36 ` Dave Page <[email protected]>
2019-02-07 09:35 ` Sandeep Thakkar <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox