I am trying to run two virtual koha on same server. That means, i am differentiating this by two different port numbers. 8080 & 8085. Now, if i want to use *two different database* for two ports, what i need to do? I think, i can clear my needs. Situation will be like this: If one wants to access: 192.168.1.233:8080 --> he/she will work on *koha * database If another one wants to access: 192.168.1.233:8085 --> he/she will work on *koha1 *database. Is it possible? -- Best, Zico
Hi,
I am trying to run two virtual koha on same server. That means, i am differentiating this by two different port numbers. 8080 & 8085. Now, if i want to use *two different database* for two ports, what i need to do? I think, i can clear my needs.
Situation will be like this:
If one wants to access: 192.168.1.233:8080 --> he/she will work on *koha * database If another one wants to access: 192.168.1.233:8085 --> he/she will work on *koha1 *database.
Is it possible?
Yes. You will have two http virtual hosts, one for each db. The only thing you have to do is to create one Koha configuration file for each vhost (so for each databasse) and define the environment variables correctly in your apache configuration file, so that the script get called with the right db info. hth, Sébastien.
I am doing named virtual hosting and it turned out to be a lot easier than I thought it would be. Two databases, two koha installs, two koha.conf files. I am doing two of everything so if one site breaks the whole thing does not go down. +---------------------------------------------------------------------+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick@state.nm.us http://www.nmstatelibrary.org -----Original Message----- From: koha-devel-bounces@lists.koha.org [mailto:koha-devel-bounces@lists.koha.org] On Behalf Of Sébastien Hinderer Sent: Monday, July 27, 2009 11:15 AM To: koha-devel@lists.koha.org Subject: Re: [Koha-devel] virtual hosting on different databases Hi,
I am trying to run two virtual koha on same server. That means, i am differentiating this by two different port numbers. 8080 & 8085. Now, if i want to use *two different database* for two ports, what i need to do? I think, i can clear my needs.
Situation will be like this:
If one wants to access: 192.168.1.233:8080 --> he/she will work on *koha * database If another one wants to access: 192.168.1.233:8085 --> he/she will work on *koha1 *database.
Is it possible?
Yes. You will have two http virtual hosts, one for each db. The only thing you have to do is to create one Koha configuration file for each vhost (so for each databasse) and define the environment variables correctly in your apache configuration file, so that the script get called with the right db info. hth, Sébastien. _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel ______________________________________________________________________ This inbound email has been scanned by the MessageLabs Email Security System. ______________________________________________________________________ Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the MessageLabs Email Security System.
Hi,
I am doing named virtual hosting and it turned out to be a lot easier than I thought it would be. Two databases, two koha installs, two koha.conf files.
Unless one Koha is used for development whereas the other one is expected to be stable, I don't think it is necessary to have wto instances of the whole code. One install plus two databases and two configuration files shoulc be enough, the apache stuff put aside. Sébastien.
On Mon, 2009-07-27 at 20:18 +0200, Sébastien Hinderer wrote:
Hi,
I am doing named virtual hosting and it turned out to be a lot easier than I thought it would be. Two databases, two koha installs, two koha.conf files.
Unless one Koha is used for development whereas the other one is expected to be stable, I don't think it is necessary to have wto instances of the whole code. One install plus two databases and two configuration files shoulc be enough, the apache stuff put aside.
I'm wondering how this applies to the Zebra config files. There are several zebra files that have directory paths which would have to be different for the two Koha installs. It would be easy enough to have modified copies of these files, and point one of the koha-conf.xml files at the copies. Just wanted to mention this caveat.
Sébastien. _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
-- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha
Michael Hafen (2009/07/27 12:32 -0600):
I'm wondering how this applies to the Zebra config files. There are several zebra files that have directory paths which would have to be different for the two Koha installs.
It would be easy enough to have modified copies of these files, and point one of the koha-conf.xml files at the copies. Just wanted to mention this caveat.
Ah, no experience with that, sorry. Cheers, Sébastien.
On Mon, Jul 27, 2009 at 2:32 PM, Michael Hafen <mdhafen@tech.washk12.org>wrote:
On Mon, 2009-07-27 at 20:18 +0200, Sébastien Hinderer wrote:
Hi,
I am doing named virtual hosting and it turned out to be a lot easier than I thought it would be. Two databases, two koha installs, two koha.conf files.
Unless one Koha is used for development whereas the other one is expected to be stable, I don't think it is necessary to have wto instances of the whole code. One install plus two databases and two configuration files shoulc be enough, the apache stuff put aside.
I'm wondering how this applies to the Zebra config files. There are several zebra files that have directory paths which would have to be different for the two Koha installs.
It would be easy enough to have modified copies of these files, and point one of the koha-conf.xml files at the copies. Just wanted to mention this caveat.
You can just do the command-line installation twice, and give it different configuration directories ("~/koha-dev" vs. '"~/koha-pro" or whatever). All the zebra and other config files will live in there for their respective installations. These are outside the codebase repository. You could have an arbitrary number of DBs running on the same code, but you will have to get remember to update each at updatedatabase time. -- Joe Atzberger LibLime - Open Source Library Solutions
participants (5)
-
Chadwick, John, DCA -
Joe Atzberger -
Michael Hafen -
Sébastien Hinderer -
Zico