Wapt 1.8 but database status is 1.7
Published: April 27, 2020 - 12:41 PM
Good morning,
Wapt server: Debian
Migration from 1.7 to 1.8
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
Wapt server: Debian
Migration from 1.7 to 1.8
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