Running Multiple Instances of OGO on the same server
"Wable, Randy" <[email protected]>
| Newsgroups | gmane.comp.cms.opengroupware.discuss.general |
|---|---|
| Message-ID | <[email protected]> |
I'm running OGo on Redhat 9 with Postgres 7.4.4. Works like a champ. The
only hurdle I have to cross now is how to setup another instance of OGo on
the same server. My goal is to run what would appear to the end users as 2
entirely separate OGo servers from the same machine. I was hoping that this
would be as easy as creating another postgres db, postgres user, duplicating
and modifying my opengroupware services file in init.d, and creating another
apache alias. I was wrong.
So I have a opengroupware file in init.d that contains the below...
OGO_ARGS="-WOPort 20000 -WOHttpAllowHost $HOSTS
-OGoMinimumActiveSessionCount 0 -LSNewsImagesUrl '/ArticleImages'
-LSNewsImagesPath '$OGO_DIR/news' LSConnectionDictionary '{databaseName =
ogo2; hostName = 127.0.0.1; password = ""; port = 5432; userName = ogo2}'
LSAdaptor PostgreSQL72 LSModelName OpenGroupware.org_PostgreSQL"
ZID_BIN="$OGO_DIR/WOApps/ZideStore.woa/ix86/linux-gnu/gnu-fd-nil/ZideStore"
ZID_ARGS="-WOPort 23000 -WOHttpAllowHost $HOSTS -SxExplain YES
-WOCachingEnabled YES -WOHttpTransactionUseSimpleParser YES"
Notice that the databaseName is ogo2. Somehow even when using this for my
first instance of ogo, this db information seems to be blatenly ignored. I
can't even get my first ogo instance to talk to a newly created db called
ogo2. It always connects to the db ogo. I figure if I can get past this, I
can adapt another service file in init.d to run the second instance of ogo.
Any thoughts on this are greatly appreciated.
Randy Wable