General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] ANN: SOGo v2.3.1


Chronological Thread 
  • From: Thomas Trepper < >
  • To:
  • Subject: Re: [SOGo] ANN: SOGo v2.3.1
  • Date: Wed, 5 Aug 2015 07:51:01 +0200


> Am 04.08.2015 um 22:21 schrieb Michal Kminek
> < >:
>
> 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
>
>
Just as an idea, if binary might not be achievable or too many efforts -
maybe the DB upgrade script can be embedded in PHP. Right after the update is
done you call a PHP script (which will have access to sogo.conf) ether
manually or this is done automatically with the first access…
Thomas




Archive powered by MHonArc 2.6.18.

Top of page