[OGo-Users] Startup script for CentOS?

[Adam Tauno Williams]

--=-ubWAKwqM4ArKAp6d+kLN
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> At 09:45 AM 2/14/2008, Adam Tauno Williams wrote:
> >I'm confused.  PostgreSQL and Apache startup scripts are provided by
> >their respective packages.  You just enable those in the normal manner;
> >just chkconfig postgresql on; chkconfig httpd2 on; and PostgreSQL and
> >Apache will start when the system boots.
>          Y'know, people might be a lot more inclined to use OGo if=20
> they got less yelled at and more helped when they asked questions

No one is yelling;  we are answering the questioned asked.  If one
doesn't understand the question it doesn't help not to say so.

> it is, I'm about an inch away from just telling my company to go with=20
> MS-Exchange for our needs.
>          Yes, I'm aware of how to make Apache and PostgreSQL start.=20
> What is less than clear is which order to start ogo-*.

It doesn't matter.  The three OGo services: WebUI, XML-RPC, and
ZideStore are not interdependent.  You may not even need to start them
all, depending on what services you need to provide.  It is actually
rather unlikely that you will need the XML-RPC daemon.  You only need
the WebUI daemon if using the provided WebUI.  You only need ZideStore
if using CalDAV, GroupDAV, WebDAV, or zOGI.

I think this is explained in WMOGAG,  but if there is a lacking bit then
specific recommendations are *very* much welcome. =20

As someone who spends a great deal of time writing documentation [most
of which never seems to get used] I admit I am quite sensitive to claims
on "no documentation";  and even more irritable about the silence after
pointing someone at the documentation and then getting no specific
criticism of why it isn't helpful.

> >You want a startup script but "rather than go through the effort" of
> >using the script provided in the CentOS packages you want a startup
> >script???  What are you actually trying to accomplish, because this
> >doesn't make any sense?
> I'm trying to start the application from one init.d script,=20
> instead of several.

Ok,  that isn't really necessary and would probably only make the
process more complicated,  especially given that in most cases you don't
need all the services on a given box.

> >Documentation is not lacking -
> >http://docs.opengroupware.org/Members/whitemice/wmogag/file_view
> >  - and even the presentation [linked to from the *HOME PAGE*] enumerate=
s
> >what is required (PostgreSQL, Cyrus, Apache, & some MTA) and the general
> >setup procedure.
> Oh -really-?
>  Go to http://www.opengroupware.org. Click on "Docs". In=20
> "Docs," click on "Plone Manual Site." You go...-nowhere-! This is=20
> because the link in the docs area is different than the links on the=20
> sidebar. Many reasonable users will go to the documentation overview=20
> to see what's available, and then click on that link, and find nothing.

I won't argue that the website is completely horrible, it is.

> So, let's say I actually figure out that the link is=20
> different in two locations, and find the right link for the Plone.=20
> Aha! I'm on the front page. Look! A link to an OGo user guide!
> Oh, wait. It doesn't work, either.
> Well, let's click on "All Docs." Oh, grand. Ten+ pages of results.
> It is, at this point, that a reasonable user will go to the=20
> mailing list, because figuring out how to get the application to run=20
> should not involve debugging the OGo site, or, alternately, digging=20
> through ten+ pages of documentation titles to find the one I'm looking fo=
r.
> Ergo -- the documentation is lacking.

Nope, it doesn't mean the same thing.  It means that documentation is
hard to get to (non-obvious),  which just isn't the same thing as saying
it doesn't exist.

As for "because figuring out how to get the application to run should
not involve debugging the OGo site", I agree 110%.  The web site is a
train wreck.

But your still overlooking the link on the right side of the *home page*
to the presentation that would answer most of your questions. =20

The link
<http://www.opengroupware.org/en/users/docs/ogo-userguide-0.9.pdf> at
the top of the Docs page entitled "Guide as PDF" loads for me;  but that
is a user's manual and not an administrator's manual.


--=-ubWAKwqM4ArKAp6d+kLN
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHtF7wLRePpNle04MRAuVkAJ9qoRXgv0TltU+ypGXIJlNVuj7WEgCbBIKw
KUm11Ly5rDV/t5G/zxv8Ri0=
=dOVp
-----END PGP SIGNATURE-----

--=-ubWAKwqM4ArKAp6d+kLN--