297d22459f
This commit makes koha-create more flexible by adding a number of command-line and configuration options. The biggest change is to add support for pre-determined MySQL credentials using a file in /etc/koha/passwd (for security reasons, if you use this feature, make sure the file is not world-readable). The configuration file has the following format: instance:user:password:database The database is optional, but the other two are both required if you want to specify MySQL credentials. If no credentials are specified for a given instance, the standard koha_instance username and an auto-generated password are used. The following additional command line options are now available: * --use-db - use a pre-existing database, see also --database * --database - specify the name of the mysql database (still defaults to koha_instance) * --passwdfile - specify a custom (Koha) passwd file for MySQL credentials The following additional variables are now available (for use in koha-sites.conf or a custom config file): * OPACPORT (previously added but not documented) - port on which the OPAC should be served * OPACPREFIX - prefix for the OPAC's virtual host * OPACSUFFIX - suffix for the OPAC's virtual host This commit also adds the --keep-mysql option to koha-remove, which, if specified, will prevent koha-remove from deleting the database or MySQL user when removing an instance. Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz> |
||
---|---|---|
.. | ||
koha-create | ||
koha-create-dirs | ||
koha-disable | ||
koha-dump | ||
koha-dump-defaults | ||
koha-email-disable | ||
koha-email-enable | ||
koha-enable | ||
koha-foreach | ||
koha-list | ||
koha-mysql | ||
koha-rebuild-zebra | ||
koha-remove | ||
koha-reset-passwd | ||
koha-restart-zebra | ||
koha-restore | ||
koha-run-backups | ||
koha-start-zebra | ||
koha-stop-zebra | ||
koha-upgrade-schema | ||
koha-upgrade-to-3.4 |