mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook- generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook-generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook- generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/ ˓→hook-generate-mo",)' You can check the effective settings Weblate is using by running: 60 Chapter 4. Administrators guide Weblate Documentation

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook-generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook- generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook- generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook-generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/hook- generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors

mode enabled, Django will show backtraces in case of error to users, when you disable it, errors will go by email to ADMINS (see above). Debug mode also slows down Weblate as Django stores much more information database supports it. The best approach is to use database native tools as they are usually most effective (eg. mysqldump or pg_dump). If you want to migrate between different databases, the only option WEBLATE_PRE_COMMIT_SCRIPTS='("${OPENSHIFT_DATA_DIR}/examples/ ˓→hook-generate-mo",)' You can check the effective settings Weblate is using by running: rhc -aweblate ssh settings This will also print syntax errors