hello guys, as i'm writting the install procedure for macports, i try to understand why th 'STANDARD' install mode exists. I never used it since i discovered the dev mode that provides simple system to update and rollback. So my documentation will refer to this strategy but i'm afraid to drive some koha users on a bad way. i really appreciate the ideas and feedbacks of all of you to know why you use the 'STANDARD' mode. regards -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com
2009/6/17 Marc Chantreux <marc.chantreux@biblibre.com>
hello guys,
as i'm writting the install procedure for macports, i try to understand why th 'STANDARD' install mode exists. I never used it since i discovered the dev mode that provides simple system to update and rollback.
So my documentation will refer to this strategy but i'm afraid to drive some koha users on a bad way. i really appreciate the ideas and feedbacks of all of you to know why you use the 'STANDARD' mode.
If you are installing from git, then the dev mode is good. If you are installing from a release tarball then standard is what most people would use. Dev mode is for people who are going to be doing updates, and rollbacks. Standard is for the majority of people who download a release, install it and leave it. Probably all the people on the devel list use the dev mode. Chris
hi Chris On Wed, Jun 17, 2009 at 10:21:52PM +1200, Chris Cormack wrote:
If you are installing from git, then the dev mode is good. If you are installing from a release tarball then standard is what most people would use.
I meant that i use git for production also because it's more quick and easy to upgrade. I never used another method than the git one even in production.
Dev mode is for people who are going to be doing updates, and rollbacks. Standard is for the majority of people who download a release, install it and leave it.
Imagine you installed koha 3.0.0, if you want to take benefits from patches (bug corrections), you are now in 3.0.2. I would like to use git as a 'aptitude update' or 'windows update'. I see it as the best practice and wonder if i missed unexpected and dangerous effects. regards -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com
2009/6/17 Marc Chantreux <marc.chantreux@biblibre.com>:
hi Chris
On Wed, Jun 17, 2009 at 10:21:52PM +1200, Chris Cormack wrote:
If you are installing from git, then the dev mode is good. If you are installing from a release tarball then standard is what most people would use.
I meant that i use git for production also because it's more quick and easy to upgrade. I never used another method than the git one even in production.
Sure lots of people do. But the average person who wants Koha for their small library probably runs off a release, not from git.
Dev mode is for people who are going to be doing updates, and rollbacks. Standard is for the majority of people who download a release, install it and leave it.
Imagine you installed koha 3.0.0, if you want to take benefits from patches (bug corrections), you are now in 3.0.2. I would like to use git as a 'aptitude update' or 'windows update'. I see it as the best practice and wonder if i missed unexpected and dangerous effects.
You can do that, but lots of people like to run from releases, and upgrade when a new release comes out. Standard mode is for them. It might be best practice for those people familiar with git, but lots of people do run from releases. Chris
Hi, On Wed, Jun 17, 2009 at 7:46 AM, Chris Cormack<chris@bigballofwax.co.nz> wrote:
You can do that, but lots of people like to run from releases, and upgrade when a new release comes out. Standard mode is for them.
Standard mode also exists for the use of packagers who want to base their package on a FHS layout as well as sysadmins who are not comfortable with the idea that an inadvertent git pull could force an upgrade. I agree that dev mode is very useful for production installations, and is probably a best practice for anybody who has to maintain multiple production Koha databases, but different strokes for different folks. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
participants (3)
-
Chris Cormack -
Galen Charlton -
Marc Chantreux