Hello Federico Alberto Sayd
On 2012-08-28 19:16, Federico Alberto Sayd wrote:
>
> I'm traying to add a new server to my sogo installation and now the
> config in the new sogo server points to the database in the original
> server, thus i had to change "localhost" by the name/ip of the original
> sogo server.
>
> But now, when I connect to the second server, although it connects to
> the database does not retrieve any data because the info about calendars
> and addressboks are hardcoded in the database with the old database
> configuration ("localhost").
>
> How I can workaround this issue?
>
For MySQL see:
http://www.mail-archive.com/[email protected]/msg00621.html
> Why the config es hardcoded in the database? Have to do with performance?
>
> This design is not flexible; changing some basic config parameters as a
> password for a database user implies to change the fields
> c_quick_location, c_acl_location and c_folder_type in the table
> sogo_folder_info.
>
Sorry, I don't know why.
And I agree it isn't flexible, and you get database passwords in plain
text from a database dump/backup.
We did circumvent this issue by using a hostname for the database which
is set via /etc/hosts on each SOGo server.
Kind regards,
Christian Mack
--
Christian Mack
Gruppe Informationsdienste
Rechenzentrum Universität Konstanz
--
[email protected]
https://inverse.ca/sogo/lists
