[OGo-Users] Install on Debian Etch or other suggestions?

[Adam Tauno Williams]

> > > I must be close .... I have succesfully completed all the
> > steps down to the
> > > point of Funomball install and figured that at this point I
> > should be able
> > > to access the Opengroupware from a browser?
> > > So do I have to get Fumombal installed BEFORE I can
> > No, you must get OpenGroupware, and its ZideStore service, working
> > first.
> OK ... so how does one do that ... :O(

It isn't hard.  If the web interface works then ZideStore will work.

> The mention of ZideStore, reminded me that it was mentioned during the
> install.

Yes, ZideStore is part of OpenGroupware.  It provides DAV, GroupDAV,
RSS, and a couple other services.  The Funambol connector requires a
GroupDAV server (ZideStore, among others).

> I made sure that TCP/IP connections are allowed in
> /etc/postgres/postgresql.conf

Still seems your package manager should have done all this.  Anyway, all
that setup is covered in WMOGAG -
http://docs.opengroupware.org/Members/whitemice/wmogag/file_view
 - if for some reason you have to do it by hand.

> But I could only find mod_include in the /etc/apache2/apache2.conf file, but
> couldn't find any mod_rewrite lines or references. For the mod_include I had
> to un-comment 30 lines in the file. After I did that the error mesage in the
> browser changed to;

If your distribution can't provide you with a decent base-line Apache
configuration you are going to have trouble.  If you have the correct
include files you just need mod_ngobjweb which should be provided via
the OGo packages.

> Each daemon has to listen on a different port for connections. Usually
> the daemons are not connected directly from application but via apache and a
> special module (mod_ngobjweb) which handles the requests. However you need
> to specify the ports the applications listen on. Its also possible to supply
> listening network  address, like so; localhost:port."
> Web user interface port (20000):
> Zidestore port (21000):
> XMLRPC daemon port (22000):

This is correct.

> The apache module forwards requests to the appropriate daemons based on the
> URL which is called. You need to specify which local part of an URL should
> be mapped to which daemon. An example: If you specify "OpenGroupware" as
> Location Match for the Web UI, OpenGroupware.org's Web UI will be available
> under "http://YOURDOMAIN/OpenGroupware".
> Web UI Location Match (OpenGroupware):
> Zidestore Location Match (zidestore):
> YMLRPC daemon  Location Match (RPC2):
> Adding user and group ogo... done.
> Set up application defaults... done.
> Set up local database... Shall the new role be allowed to
> create more new roles? (y/n)
> Initialization of OpenGroupware.org instance finished. Now make sure
> OpenGroupware.org can access the specified database. Check
> /etc/postgres/postgresql.conf if TCP/IP connections are allowed.
> Also verify that a suitable accessmethod is enabled in
> /etc/postgresql/pg_hba.conf.

Did you check the logs, as described earlier, so see if the OGo daemons
made connection with PostgreSQL?

> Please note that you need to have mod_include and mod_rewrite enabled in
> apache for this configuration working out of the box. 

mod_rewrite must be a requirement of how this create session script sets
things up.

> They are enabled by default in apache 1.3, but are not in apache 2.