From ca49afe2708909b66e076ba0a6fd833e62c7cec0 Mon Sep 17 00:00:00 2001 From: Thorsten Eckel Date: Thu, 3 Dec 2020 10:05:30 +0100 Subject: [PATCH] Maintenance: Fixed typos. --- contrib/backup/functions | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/contrib/backup/functions b/contrib/backup/functions index 5afd73db4..361ba641f 100644 --- a/contrib/backup/functions +++ b/contrib/backup/functions @@ -1,6 +1,6 @@ #!/usr/bin/env bash # -# zammad backup script functions +# Zammad backup script functions # function get_zammad_dir () { @@ -64,7 +64,7 @@ function check_database_config_exists () { if [ -f ${ZAMMAD_DIR}/config/database.yml ]; then get_db_credentials else - echo -e "${ZAMMAD_DIR}/config/database.yml is missing. is zammad configured yet? \nAborting..." + echo -e "${ZAMMAD_DIR}/config/database.yml is missing. is Zammad configured yet? \nAborting..." exit 1 fi } @@ -164,14 +164,14 @@ function restore_zammad () { if ! id "zammad" &> /dev/null; then echo "# ERROR: User 'zammad' is not present, but should be by default! #" - echo "# Restoration was NOT successfull, exitting ..." + echo "# Restoration was NOT successful, exiting ..." exit 1 fi - + echo "# ... Dropping current database ${DB_NAME}" # This step is only needed for some pgsql dumps, as they don't provide a drop table statement which will cause - # relation errors during restoration (as on package installation there's always an initialised database) + # relation errors during restoration (as on package installation there's always an initialized database) if command -v zammad > /dev/null; then zammad config:set DISABLE_DATABASE_ENVIRONMENT_CHECK=1 zammad run rake db:drop