On 7/30/2015 9:30 AM, Steve Ankeny wrote:
On 07/30/2015 09:14 AM, Christian Mack wrote:
Am 30.07.2015 um 15:05 schrieb Chris Coleman:
On 7/30/2015 8:57 AM, Christian Mack wrote:
Hello
Am 30.07.2015 um 14:24 schrieb Márcio Merlone:
On 24-07-2015 08:07, Steve Ankeny wrote:
The only issues I remember with the running of the script were --
(1) users fail to run it
(2) or, they run the wrong script
Instructions are *always* at the back pages of the Installation
Guide --
http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg
58)
Since I run Ubuntu, I assume the install/upgrade procedure from apt
already does that, is this correct?
No!
You have to do that manually.
Kind regards,
Christian Mack
I nominate adding the database schema upgrade script to the deb and rpm
install/upgrade scripts. It would need to detect the current db schema
version and apply the appropriate db updates. Which it surely does
already...
That automation alone would probably reduce friction by 5%.
It is not that easy.
It first would have to scan your config, in order to find which DBMS you
use.
Some are even using multiple DBs.
Kind regards,
Christian Mack
I nominate a having a warning PLEASE READ INSTRUCTIONS before upgrading!
It's very clearly spelled out in the instructions (as well as in
various places on this mailing list)
Yes, but I believe the goal is (and needs to be) zero-effort upgrades,
to whatever extent possible within reason.
For the admins using 3 different database engines, to provide separate
login (microsoft ldap), session (mysql in memory), and data storage
(postgres) , to achieve extreme high performance, maybe we can let them
risk manually running db schema upgrade scripts (and run the wrong
versions of the schema scripts, or completely forget to run them), but
even then, a config file parser class should automatically extract those
3 sets of db credentials from sogo.conf and perform automated schema
upgrades.
--
[email protected]
https://inverse.ca/sogo/lists
