Page 1 of 1

Wapt 1.8 but database status is 1.7

Published: April 27, 2020 - 12:41 PM
by jojo57
Good morning,

Wapt server: Debian
Migration from 1.7 to 1.8
2020-04-27 12_31_39-WAPT - Apt-get for Windows.jpg
2020-04-27 12_31_39-WAPT - Apt-get for Windows.jpg (12.57 KB) Viewed 4513 times
I just updated Wapt from version 1.7 to version 1.8 without any problems; I'm now running Debian Buster and Wapt 1.8
Everything seems to be working fine (I haven't deployed any packages in Wapt 1.8 yet) but the database version is still in Wapt 1.7 (I did the update procedure to PostgreSQL 11 as in the documentation).
I successfully completed the postconf and restarted the server.

Is this normal/a problem? And if so, how do I update the database?
THANKS


PS: I should clarify that I updated Wapt to version 1.8 on the Debien Stretch server, and then upgraded from Stretch to Buster. I tried doing the opposite, migrating from Stretch to Buster first and then upgrading Wapt, but in that case, I lose the web server, which crashes every time

Re: Wapt 1.8 but database status is 1.7

Published: April 27, 2020 - 1:46 PM
by sfonteneau
No worries, that's normal; the latest version of the database on our end is 1.7.6.6

Re: Wapt 1.8 but database status is 1.7

Published: April 29, 2020 - 10:11 AM
by jojo57
Okay, I'm relieved, thank you very much, and keep it up, Wapt is really great!

Re: Wapt 1.8 but database status is 1.7

Published: April 29, 2020 - 11:01 AM
by vcardon
A fix is ​​coming in the next WAPT release to ensure the database version follows the server version, regardless of whether the database schemas have changed or not, as we have received your feedback several times.

Indeed, the database version was used to indicate the last time the PGSQL schemas were updated, but we've noticed this is causing confusion.

Sincerely,

Vincent

Re: Wapt 1.8 but database status is 1.7

Published: April 29, 2020 - 12:49 PM
by jojo57
Thank you for the reply; indeed, it can be confusing with a different version number.

Thank you.