Re: Require suggestions on feature #5766
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
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 wrote:
>
>> Hi
>>
>> On Wed, 16 Apr 2025 at 11:38, Anil Sahoo
>> 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”: 9,
>>> “download_url”: “
>>> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads”,
>>> “auto_update_url”: {
>>> “macOS”: ““,
>>> “windows”: “”
>>>}
>>> },
>>> “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
>>> wrote:
>>>
Okay, I will implement it as per the suggestions.
Thanks
On Wed, Mar 19, 2025 at 5:14 PM Dave Page wrote:
>
>
> On Wed, 19 Mar 2025 at 10:58, Anil Sahoo
> 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 || *G
Re: pgAdmin logo contribution
Oh awesome, definitely not saying either/or when it comes to contributions, and understood that proposing a logo doesn't mean yall would accept it, just like with code contributions! :) On Wed, Apr 16, 2025 at 3:55 PM Dave Page wrote: > > Hi Floor! > > On Wed, 16 Apr 2025 at 12:34, Floor Drees > wrote: >> >> Hi pgAdmin team, hey Dave! >> >> I talked to Akshay and he mentioned that reaching out here is the best next >> step. I've secured a little design time to spend on contributing to open >> source projects. >> >> Having been a maintainer, I know that code contributions you'll get, but >> people making you a logo, or helping with marketing stuff is very VERY rare. >> >> For instance: CloudNativePG will get a little brand and website TLC, and I >> was thinking maybe seeing if pgAdmin would be interested to as a way of >> contributing get (a) logo(s ideas). >> >> How fun would it be if we could have pgAdmin stickers to hand out at >> conferences? >> >> What do you think?! And how would you like me to move forward? > > > If you have proposals for a logo, I'll certainly consider them, as I'm sure > would the other dev team members. Please do keep in mind though, that pgAdmin > hasn't had a logo in the 27 or so years it's been in existence, so I think > it's safe to say we'd have to fall in love with a proposal in order to adopt > it. > > I would suggest that non-code contributions such as string review/revision, > or doc improvements would be more valuable to the project, if that's > something that interests you. > > Thanks, Dave. > > -- > Dave Page > pgAdmin: https://www.pgadmin.org > PostgreSQL: https://www.postgresql.org > pgEdge: https://www.pgedge.com >
Re: Require suggestions on feature #5766
Hi
On Wed, 16 Apr 2025 at 11:38, Anil Sahoo
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”: 9,
> “download_url”: “
> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads”,
> “auto_update_url”: {
> “macOS”: ““,
> “windows”: “”
>}
> },
> “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
> wrote:
>
>> Okay, I will implement it as per the suggestions.
>>
>> Thanks
>>
>> On Wed, Mar 19, 2025 at 5:14 PM Dave Page wrote:
>>
>>>
>>>
>>> On Wed, 19 Mar 2025 at 10:58, Anil Sahoo
>>> 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 || *GitHub
>> *
>>
>> enterprisedb.com
>>
>
>
> --
>
>
> *Anil Sahoo*
>
> Software Development Engineer II
>
> LinkedIn || *GitHub
> *
>
> enterprisedb.com
>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
Re: pgAdmin logo contribution
Hi Floor! On Wed, 16 Apr 2025 at 12:34, Floor Drees wrote: > Hi pgAdmin team, hey Dave! > > I talked to Akshay and he mentioned that reaching out here is the best > next step. I've secured a little design time to spend on contributing to > open source projects. > > Having been a maintainer, I know that code contributions you'll get, but > people making you a logo, or helping with marketing stuff is very VERY rare. > > For instance: CloudNativePG will get a little brand and website TLC, and I > was thinking maybe seeing if pgAdmin would be interested to as a way of > contributing get (a) logo(s ideas). > > How fun would it be if we could have pgAdmin stickers to hand out at > conferences? > > What do you think?! And how would you like me to move forward? > If you have proposals for a logo, I'll certainly consider them, as I'm sure would the other dev team members. Please do keep in mind though, that pgAdmin hasn't had a logo in the 27 or so years it's been in existence, so I think it's safe to say we'd have to fall in love with a proposal in order to adopt it. I would suggest that non-code contributions such as string review/revision, or doc improvements would be more valuable to the project, if that's something that interests you. Thanks, Dave. -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org pgEdge: https://www.pgedge.com
Re: Require suggestions on feature #5766
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 wrote:
> Hi
>
> On Wed, 16 Apr 2025 at 11:38, Anil Sahoo
> 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”: 9,
>> “download_url”: “
>> https://www.enterprisedb.com/downloads/postgres-postgresql-downloads”,
>> “auto_update_url”: {
>> “macOS”: ““,
>> “windows”: “”
>>}
>> },
>> “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
>> wrote:
>>
>>> Okay, I will implement it as per the suggestions.
>>>
>>> Thanks
>>>
>>> On Wed, Mar 19, 2025 at 5:14 PM Dave Page wrote:
>>>
On Wed, 19 Mar 2025 at 10:58, Anil Sahoo
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 || *GitHub
>>> *
>>>
>>> enterprisedb.com
>>>
>>
>>
>> --
>>
>>
>> *Anil Sahoo*
>>
>> Software Development Engineer II
>>
>> LinkedIn || *GitHub
>> *
>>
>> enterpris
Re: Require suggestions on feature #5766
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”: 9,
“download_url”: “
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads”,
“auto_update_url”: {
“macOS”: ““,
“windows”: “”
}
},
“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/”
}
}
}
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.
Thanks,
Anil
On Wed, Mar 19, 2025 at 6:53 PM Anil Sahoo
wrote:
> Okay, I will implement it as per the suggestions.
>
> Thanks
>
> On Wed, Mar 19, 2025 at 5:14 PM Dave Page wrote:
>
>>
>>
>> On Wed, 19 Mar 2025 at 10:58, Anil Sahoo
>> 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 || *GitHub
> *
>
> enterprisedb.com
>
--
*Anil Sahoo*
Software Development Engineer II
LinkedIn || *GitHub
*
enterprisedb.com
pgAdmin logo contribution
Hi pgAdmin team, hey Dave! I talked to Akshay and he mentioned that reaching out here is the best next step. I've secured a little design time to spend on contributing to open source projects. Having been a maintainer, I know that code contributions you'll get, but people making you a logo, or helping with marketing stuff is very VERY rare. For instance: CloudNativePG will get a little brand and website TLC, and I was thinking maybe seeing if pgAdmin would be interested to as a way of contributing get (a) logo(s ideas). How fun would it be if we could have pgAdmin stickers to hand out at conferences? What do you think?! And how would you like me to move forward? Have a great day everyone! Floor
