I overheard somewhere (though I can't remember the details) that using
the dev install mode makes it easier to upgrade koha. I've never done a
koha upgrade; we're not fully migrated yet, but I'd like to facilitate
future upgrades as much as possible.
I've had no problem setting up a koha standard install; when I try a dev
install, my zebra server won't run. The server reports on boot up (and
when I manually start Zebra) that it is starting the Zebra Daemon and
Zebra Server, but when I look for the process (top -c), it's not there.
No error messages are generated when starting the server.
Is there something special that must be done with Zebra conf on a dev
install?
Can someone explain the advantages of a dev install? I understand that
it allows you to run the majority of the koha server files directly from
a git clone. I see how this could simplify an upgrade, but are there
other advantages that will encourage me to get to the bottom of this?
Thanks for your time.
--
Cheers,
Christopher Curry
Assistant Technical Librarian / Assistant IT Officer
American Philosophical Society
105 South Fifth Street
Philadelphia, PA 19106-3386
Tel. (215) 599-4299
ccu...@amphilsoc.org <mailto:ccu...@amphilsoc.org>
*For technical support, please use helpd...@amphilsoc.org
<mailto:helpd...@amphilsoc.org>*
Main Library number: (215)440-3400
APS website: http://www.amphilsoc.org
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
