Dne 4.8.2015 v 11:38 Marc Patermann napsal(a):
Hi,
Am 30.07.2015 um 15:05 Uhr schrieb Chris Coleman:
On 7/30/2015 8:57 AM, Christian Mack wrote:
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.
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%.
whatever is done, remember:
The db don't have to be on the same host as the SOGo daemon is!
We have i.e. have multiple SOGo frontend server and a postgresql
cluster (with pgpool) in the background.
Single server scenarios are not all there is.
Marc
I agree but SOGo always accesses its database using a defined connection
from sogo.conf. The same connection can be used to deliver a DB update.
It's not important if the database is on the same server. I have no
experience with pgpool but I believe any DB update can be delivered too.
It would be really helpful if these DB changes come with the
corresponding binary packages.
Michal
--
users@sogo.nu
https://inverse.ca/sogo/lists
