Re: [SOGo] Migrating to SOGo
Hello Quentin, Thanks for answering my questions, appreciate it. Kind regards On Thu, Jul 6, 2023 at 4:29 PM qhivert wrote: > > Hello, > Thanks for your interest in sogo ! Here your answers: > > 1. Yes, you will just have to change the repo link on your > /etc/apt/sources.list.d/SOGo.list file. > 2. No, you will have a private Bug Tracker System where only you and Alinto > will be able to see your tickets. > 3. No feature differences between the stable and nightly apart the ones that > are in development. > 4. For now, Alinto tries to make a release every 3/4 month. But is has > already happened that, if a bug is major/blocker, a new release is made as > soon as possible. > > Regards, > Quentin > > -Original Message- > From: users-requ...@sogo.nu On Behalf Of Kenren Taisho > Sent: mercredi 5 juillet 2023 10:35 > To: users@sogo.nu > Subject: [SOGo] Migrating to SOGo > > Hello. > We are in the process of migrating our current groupware to SOGo and would > like to clarify the following: > > 1. We are currently using the nightly build for testing but will eventually > use the stable build and will subscribe to premium support service. Is it > just a matter of switching the repository from nightly to stable and do a > package manager system update? > 2. Is the support portal mentioned on the commercial page this same mailing > list? > 3. Is there no feature difference between the nightly build and the stable > build? > 4. If a bug is fixed in the nightly build, how soon does that fix reflect in > the stable build? > > Apologies for all the questions and thanks in advance for the answers. > > > Kind regards >
RE: [SOGo] Migrating to SOGo
Hello, Thanks for your interest in sogo ! Here your answers: 1. Yes, you will just have to change the repo link on your /etc/apt/sources.list.d/SOGo.list file. 2. No, you will have a private Bug Tracker System where only you and Alinto will be able to see your tickets. 3. No feature differences between the stable and nightly apart the ones that are in development. 4. For now, Alinto tries to make a release every 3/4 month. But is has already happened that, if a bug is major/blocker, a new release is made as soon as possible. Regards, Quentin -Original Message- From: users-requ...@sogo.nu On Behalf Of Kenren Taisho Sent: mercredi 5 juillet 2023 10:35 To: users@sogo.nu Subject: [SOGo] Migrating to SOGo Hello. We are in the process of migrating our current groupware to SOGo and would like to clarify the following: 1. We are currently using the nightly build for testing but will eventually use the stable build and will subscribe to premium support service. Is it just a matter of switching the repository from nightly to stable and do a package manager system update? 2. Is the support portal mentioned on the commercial page this same mailing list? 3. Is there no feature difference between the nightly build and the stable build? 4. If a bug is fixed in the nightly build, how soon does that fix reflect in the stable build? Apologies for all the questions and thanks in advance for the answers. Kind regards
Re: [SOGo] Migrating/Merging SOGo database(s)
Hi Sven > On May 15, 2019, at 5:48 AM, Sven Schwedas (sven.schwe...@tao.at) > wrote: > > Currently, we have a SOGo setup where each branch office has their own > server, with separate databases, and users log into their respective > branch. This obviously leads to various problems (calendar subscriptions > across branches are a pain, etc.); so we want to merge it all into one > instance. > > • Table names for each user are predictable and not randomized, so I can > take the user tables, the user's sogo_folder_info rows, and > sogo_user_profile row from the user's server and just merge them > together, correct? Correct, as long as all c_uid are unique. > • In sogo_folder_info, I need to update the c_*location columns to have > the correct new URIs; are any other changes needed? That's it. > • In particular, where/how are subscriptions tracked and do I need to > make any changes to make them work on the new instance? Subscriptions are in the c_settings (sogo_user_profile), but don't include the full URI. So you should not have to manipulate this column unless you used "Web calendars" to view the calendars of a remote SOGo server. Francis -- users@sogo.nu https://inverse.ca/sogo/lists
