Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gerard.flanagan@outlook.com
 designates 157.55.0.207 as permitted sender)
Message-ID: <DUB002-W1171BE70B8255BF96800BE0F9F40@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_976f2ce9-b52c-4c14-b08b-34007a26b9cf_"
From: Gerard Flanagan <gerard.flanagan@outlook.com>
To: "bloodhound-dev@incubator.apache.org"
	<bloodhound-dev@incubator.apache.org>
Subject: RE: Buildout dev environment
Date: Mon, 18 Feb 2013 07:54:52 +0000
Importance: Normal
In-Reply-To: 
 <CAGMZAuP27fuuLgUUULp9=2TAqn_nFh=Nku8WgMN5nzpNdCnPwQ@mail.gmail.com>
References: 
 <DUB002-W10CF0A08D0E1517CFBD7DCD10D0@phx.gbl>,<CAGMZAuP27fuuLgUUULp9=2TAqn_nFh=Nku8WgMN5nzpNdCnPwQ@mail.gmail.com>
MIME-Version: 1.0

--_976f2ce9-b52c-4c14-b08b-34007a26b9cf_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Thanks
>=20
> What about creating a second Apache=99 Bloodhound instance (i.e environme=
nt) ?
>=20

You would more or less repeat the process in another directory and change t=
he relevant parameters in the buildout.cfg file - project name=2C database =
name etc. - before running ./bin/buildout. A common environments directory =
ought to be possible. (The actual instance package name need not be changed=
 from 'bhinstance' just the directory in which 'bhinstance' is found - if f=
ile paths are correct in buildout.cfg then buildout will do the relevant sy=
s.path setup such that the correct 'bhinstance' is imported).
For running multiple instances behind a web server=2C I would use uwsgi rou=
ter/subscription server so that you can add or remove instances without nee=
ding to stop/restart the frontend.
GMF

 		 	   		  =

--_976f2ce9-b52c-4c14-b08b-34007a26b9cf_--