bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gerard Flanagan <>
Subject RE: Buildout dev environment
Date Tue, 19 Feb 2013 06:44:21 GMT

> What about creating a second Apacheā„¢ Bloodhound instance (i.e environment) ?

You would more or less repeat the process in another directory and change the relevant parameters
in the buildout.cfg file - project name, 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 file
paths are correct in buildout.cfg then buildout will do the relevant sys.path setup such that
the correct 'bhinstance' is imported).
For running multiple instances behind a web server, I would use uwsgi router/subscription
server so that you can add or remove instances without needing to stop/restart the frontend.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message