public inbox for [email protected]
help / color / mirror / Atom feedFrom: Anil Sahoo <[email protected]>
To: Dave Page <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Subject: Re: Require suggestions on feature #5766
Date: Thu, 17 Apr 2025 11:36:52 +0530
Message-ID: <CAO+oWtCxKLGVKdGP267o1tE6huwpBbQ6XusE4QXZMo3-QF8T_w@mail.gmail.com> (raw)
In-Reply-To: <CAO+oWtAYupYzWmPhpzLc0YD7bY+DYh-_GkOC=kbberJ8essxyw@mail.gmail.com>
References: <CAO+oWtDcnBcAP+xNyvJ3z2MydKaGGZTZTXbucuU5_J6u+-yEcQ@mail.gmail.com>
<CA+OCxozfcxstPaX8pLKUtFAiYT8z30EKnRs0OmLn+x7Yc7CzhQ@mail.gmail.com>
<CAO+oWtAFUkU100ATF0eK7bVK0-RWfPmV4qHZk+J5euSHTy+M3g@mail.gmail.com>
<CA+OCxoztMFO24ZYSsNnX98zTnxst4uLpaN4qK+2jEwyyJwnAKQ@mail.gmail.com>
<CAO+oWtBKzSNxeNUwfK31wgfZ71X2-zOh-avYxwwO2dT3kff0yQ@mail.gmail.com>
<CA+OCxozz4eKUB=OEgNCC=k70GGmpuQ+8HyFaTPjduB7ghFp+TQ@mail.gmail.com>
<CAO+oWtAizZMgEAHfQ5A5-X_DwXrVU2Gsx1yq9oDNjp9ZE6EY1Q@mail.gmail.com>
<CA+OCxox-YgkAv9BM8TAAkayfOzXQeLrauFA+1J1f4Y=WWPp9dQ@mail.gmail.com>
<CAO+oWtAhjVFb1UKB9h2hxGKLLA4c9qU=hwEDvfRQTG_QN0N77A@mail.gmail.com>
<CAO+oWtDZdXgNbj7=Fw+nChnM7fb=ayr9ZeGGdT_2KdPfUDC+3w@mail.gmail.com>
<CA+OCxoxTvtP_yYGnh39WgtO9gmoxkBMNqQio+0NajLQyb7_s9A@mail.gmail.com>
<CAO+oWtAYupYzWmPhpzLc0YD7bY+DYh-_GkOC=kbberJ8essxyw@mail.gmail.com>
Hi Dave,
FYI auto_update_url can be anything, and it's optional to give a version
number.
Thanks
On Thu, Apr 17, 2025 at 11:06 AM Anil Sahoo <[email protected]>
wrote:
> Hi Dave,
>
> Yes zip files will have the version number, here is an
> example: pgadmin4-9.2-arm64.zip.
>
> Yes, version number will be included in the earlier mentioned URL.
>
> Also I will keep the field names in lower case.
>
> Thanks
>
> On Wed, Apr 16, 2025 at 7:15 PM Dave Page <[email protected]> wrote:
>
>> Hi
>>
>> On Wed, 16 Apr 2025 at 11:38, Anil Sahoo <[email protected]>
>> wrote:
>>
>>> Hi Dave,
>>>
>>> As we discussed in the last meeting, along with your suggestion to add a
>>> key in pgaweb's versions.json indicating the source URL for downloading
>>> updates for the auto-update feature, I propose the following approach. We
>>> will need to make corresponding changes in the pgaweb repository to
>>> support this.
>>>
>>> *Example versions.json format:*
>>>
>>> {
>>>
>>> “edb-pgadmin4”: {
>>> “version”: “9.0”,
>>> “version_int”: 90000,
>>> “download_url”: “
>>> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads”,
>>> “auto_update_url”: {
>>> “macOS”: “<edb_installer_url>“,
>>> “windows”: “<edb_installer_url>”
>>> }
>>> },
>>> “pgadmin4”: {
>>> “version”: “9.2”,
>>> “version_int”: 90200,
>>> “download_url”: “https://www.pgadmin.org/download/”,
>>> “auto_update_url”: {
>>> “macOS”: “
>>> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/v9.2/macos/”,
>>> “windows”: “
>>> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/v9.2/windows/”
>>> }
>>> }
>>> }
>>>
>> Yes, that seems reasonable - except I'd keep the field names all in lower
>> case.
>>
>>
>>> Additionally, as I mentioned earlier, for Electron’s auto-update to
>>> function on macOS, we need to provide a zip installer that contains the pgAdmin
>>> 4.app.
>>>
>>> If we maintain zip installers for both arm64 and x86_64 macOS
>>> architectures, and potentially extend auto-update support to Windows in the
>>> future, we estimate requiring up to 1.5 GB of additional storage on the FTP
>>> server beyond the current allocation. Please note that we only need to
>>> store the zip files for the latest version, as older versions will be
>>> updated directly to the newest release.
>>>
>>> Please share your suggestions on this.
>>>
>> Do the zip files include the version number (and is that also included in
>> the URLs above)?
>>
>>
>>> Thanks,
>>> Anil
>>>
>>> On Wed, Mar 19, 2025 at 6:53 PM Anil Sahoo <[email protected]>
>>> wrote:
>>>
>>>> Okay, I will implement it as per the suggestions.
>>>>
>>>> Thanks
>>>>
>>>> On Wed, Mar 19, 2025 at 5:14 PM Dave Page <[email protected]> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, 19 Mar 2025 at 10:58, Anil Sahoo <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi Dave,
>>>>>>
>>>>>> As discussed I moved with auto-update of pgAdmin 4 application in
>>>>>> macOs system locally. It is successful.
>>>>>> So now I have to do some additional user experience improvements.
>>>>>>
>>>>>> Listing down some ways we can show the user that a new version is
>>>>>> available and he can download and install it.
>>>>>>
>>>>>> *Option 1:*
>>>>>>
>>>>>> Show a dialog with the released features and fixes(mentioned in the
>>>>>> release note) with *"Download & Restart"* and *"Cancel"* buttons.
>>>>>> This dialog will be shown only when the application starts for the first
>>>>>> time of the day.
>>>>>>
>>>>>> Benefits of showing this dialog will help users to know about the new
>>>>>> features and bugs fixed available in the latest version.
>>>>>>
>>>>>> "Download & Restart" button will download the latest version and quit
>>>>>> the app and install and open the latest app. "Cancel" will cancel
>>>>>> the notification.
>>>>>>
>>>>>> *Option 2:*
>>>>>>
>>>>>> We are currently showing a warning notification of the latest version
>>>>>> available, if the older version is being used by the user, we can add *"Download
>>>>>> & Restart"* and *"Cancel" * buttons. And those buttons will work the
>>>>>> way they are working in Option 1.
>>>>>>
>>>>>> Additionally we will add *"Check for updates"* option in pgAdmin 4
>>>>>> native menu, if any time a user wants to check for updates manually then
>>>>>> can prefer this and if update is available then the *"Restart to
>>>>>> update"* option will show and if clicked will quit the app and
>>>>>> install the latest version.
>>>>>>
>>>>>> Let me know in which way we can proceed.
>>>>>>
>>>>>
>>>>> Option 1 seems good to me; though the current notifier should continue
>>>>> to work as it does now if a particular distribution channel doesn't support
>>>>> auto-updates (for example, the EDB PostgreSQL Installer).
>>>>>
>>>>> --
>>>>> Dave Page
>>>>> pgAdmin: https://www.pgadmin.org
>>>>> PostgreSQL: https://www.postgresql.org
>>>>> pgEdge: https://www.pgedge.com
>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> *Anil Sahoo*
>>>>
>>>> Software Development Engineer II
>>>>
>>>> LinkedIn <https://www.linkedin.com/in/anilksahoo9/; || Blog
>>>> <https://www.enterprisedb.com/anil-sahoo; || *GitHub
>>>> <https://github.com/anilsahoo20>*
>>>>
>>>> enterprisedb.com
>>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Anil Sahoo*
>>>
>>> Software Development Engineer II
>>>
>>> LinkedIn <https://www.linkedin.com/in/anilksahoo9/; || Blog
>>> <https://www.enterprisedb.com/anil-sahoo; || *GitHub
>>> <https://github.com/anilsahoo20>*
>>>
>>> enterprisedb.com
>>>
>>
>>
>> --
>> Dave Page
>> pgAdmin: https://www.pgadmin.org
>> PostgreSQL: https://www.postgresql.org
>> pgEdge: https://www.pgedge.com
>>
>>
>
> --
>
>
> *Anil Sahoo*
>
> Software Development Engineer II
>
> LinkedIn <https://www.linkedin.com/in/anilksahoo9/; || Blog
> <https://www.enterprisedb.com/anil-sahoo; || *GitHub
> <https://github.com/anilsahoo20>*
>
> enterprisedb.com
>
--
*Anil Sahoo*
Software Development Engineer II
LinkedIn <https://www.linkedin.com/in/anilksahoo9/; || Blog
<https://www.enterprisedb.com/anil-sahoo; || *GitHub
<https://github.com/anilsahoo20>*
enterprisedb.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Require suggestions on feature #5766
In-Reply-To: <CAO+oWtCxKLGVKdGP267o1tE6huwpBbQ6XusE4QXZMo3-QF8T_w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox