Among other things, we apparently need to force install of Yaz, at least
until indexdata fixes or forgoes a dependence on their remote test server
(and your open firewall allowing access to it).
Argh, not that problem again! I had hoped they would have learned from
the last time.
Dan Scott wrote:
2009/9/3 Joe Atzberger a...@esilibrary.com
Also need to add a2enmod xmlent, but at a later point after that
EG-specific piece is compiled and available, before the apache restart.
Hmm. I don't think anyone else has mentioned this as a requirement
before; is that new with
Mike Rylander wrote:
On Tue, Sep 1, 2009 at 11:03 PM, Joe Atzbergera...@esilibrary.com wrote:
Evergreen's Apache configuration has to play nice with others. Users might
quite reasonably want to install/use phpPGadmin, ReservesDirect, gitweb,
their old ILS, or even another instance of
On 02/09/2009, Joe Atzberger a...@esilibrary.com wrote:
I'm not trying to make the decision whether SSL is required for
Evergreen or not. In fact, I explicitly added to the documentation:
a2enmod ssl# enable mod_ssl
If I recall correctly, that step is already in Makefile.install
Dan Scott wrote:
On 02/09/2009, Joe Atzberger a...@esilibrary.com wrote:
I'm not trying to make the decision whether SSL is required for
Evergreen or not. In fact, I explicitly added to the documentation:
a2enmod ssl# enable mod_ssl
If I recall correctly, that step is
2009/9/2 Joe Atzberger a...@esilibrary.com:
Dan Scott wrote:
On 02/09/2009, Joe Atzberger a...@esilibrary.com wrote:
I'm not trying to make the decision whether SSL is required for
Evergreen or not. In fact, I explicitly added to the documentation:
a2enmod ssl # enable mod_ssl
Evergreen's Apache configuration has to play nice with others. Users
might quite reasonably want to install/use phpPGadmin, ReservesDirect,
gitweb, their old ILS, or even another instance of evergreen under a
different user. That basically comes down to us being more articulate
about
