I know that it is not a problem of sogo, but i'm a developer and not a
system administrator. I mean if I really want to make use of sogo i
wouldn't want to go through thousands of documentations, just to have a
good and working installation.

i mean, you configured your apache right? i don't think so. i mean i've
spent a week, fulltime to make the best available configuration, just for a
python deployment with mod_wsgi. it contains only the things that are
needed to  work. also i've spent hours with mod_proxy and nginx as a proxy
pass or haproxy.
i've did this since i needed it.

I've currently doing the same with Postgresql and 389 Directory Server. But
still it's a lot of stuff and I could do that in fulltime. But how much
people have that much time in their company? Most people won't they need to
show some things and than deploy it or even the people who want it for
their home servers, they want to make things work, not to spent their whole
life by configure and evolve the process of deployments.

You ever used Microsoft Exchange?
I Could configure and install / deploy it in under 4 hours, fully
configured and working (without used it before). Do you really think that
ANYBODY could do that with sogo?
I mean you ever seen a good documentation? Look at the Zimbra
Documentation. In the Single Server install guide you could install Zimbra
from Zero to Working and Zimbra still uses OpenLDAP, Postfix and Apache.
Could you do that with sogo? No. The Documentation won't have the required
things.
Or take a look at the FreeIPA Docs here:
>
http://docs.fedoraproject.org/en-US/Fedora/18/html/FreeIPA_Guide/index.html
There is a shitload of stuff but it's organized and you could easily use
freeipa.

Trust me sogo is great. But to deploy it you need a really really long
time. Especially in good enviroments.





2013/7/7 Szládovics Péter <[email protected]>

> 2013-07-07 19:59 keltezéssel, [email protected] írta:
>
>  It's true what you are saying, currently i'm planning some sogo
>> deployments,
>> one with a LDAP (FreeIPA) Backend and one with a postgresql Backend.
>> Currently
>> I'm playing around with postgresql and it isn't really easy with this
>> documentation to bring up SOGo. (But btw. other Groupware Documentations
>> are
>> painful aswell)
>> I mean SOGo is really really good. It's very fast and it works on my VPS
>> that
>> has 512MB Memory even with LDAP installed. (Currently Zimbra needs way
>> more 2GB
>> Memory or above, that makes it painful to use, but easy to install /
>> configure).
>>
>> I think the problem with the documentation is not the configuration
>> steps, Some
>> things are just missing. I mean when I want to configure SOGo, I wan't to
>> know,
>> how I configure Cyrus with any SOGo Backend aswell and Postfix also with
>> any
>> Backend. I mean I'm confident with Apache and i wouldn't even needed the
>> config
>> file that you deployed with sogo. But I'm a total newbie with ldap /
>> postfix /
>> cyrus and I think many people are new to this feature aswell, since most
>> of the
>> groupware people coming from other enviroments where you didn't need to
>> configure your own imap or mta.
>>
>> Nothing against you sogo guys, since you gave us one of the best,
>> groupware's
>> that are completly free and there aren't good alternatives. I mean
>> kolab3, is
>> really not production ready, zimbra is not really good since the nice
>> features
>> are only in the network edition and it uses way to much ressources, horde
>> is
>> cool and good, but it's old and still uses more than sogo uses. there are
>> plenty of examples why sogo is better, but since you gave us 1 Document
>> with
>> like 60 sites which only includes the options that i could configure
>> about sogo
>> and not a complete document HOW TO INSTALL sogo it's really hard.
>>
>> I mean rename the document from SOGo installation to SOGO Configurable
>> Options
>> and make a new Guide which says Install Sogo which includes nearly every
>> configuration option for real world deployments.
>>
>
> Guys, it's absolutelly right!
> But... If anybody newbie in postgres/mysql or in any ldap, or
> dovecot/cyrus/courier or postfix/sendmail/exim or _wathever what is not
> sogo, just a backend_ - is this problem of documentation of sogo? I dont
> think so...
> At the begin of this year I never yet used Dovecot. I didn't install and
> use any OpenLDAP/Samba 4 instances. I knew postfix (but not in ldap auth),
> and knew mysql, and I knew apache.
> Understanding some dovecot mechanism was a little bit hard - quota+ldap,
> folder sharing+ldap, sieve (pigeonhole). Samba 4 and openchange was
> absolutelly new for me.
> AFAIK I did 30-40 installs with failed or almost worked status, and
> reinstalled them, and again, and again - and learn.
> You need to know, everybody thinks otherwise. My config is probably won't
> good for you, and your problem is probably not similar to my problem.
> So, I can't help - not 'don't want', just 'can't'.
> But when your problem is same or similar with one of my problems, I can
> help, and I will help.
>
> I think this community is helpful, when it can.
>
> /Sorry my bad English/
> --
> [email protected]
> https://inverse.ca/sogo/lists
>
-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to