Commit 489ab804 authored by Giorgos Kazelidis's avatar Giorgos Kazelidis

- Added the "Artemis" and "DSpace@NTUA" digital repository URLs of the diploma thesis to README.md

- Made some corrections/enhancements (e.g. corrected the "utf8mb4_0900_ci_ai" database collation to "utf8mb4_0900_ai_ci") to the instructions in settings.py and README.md
parent cbb4ff8b
## PROJECT OVERVIEW ## PROJECT OVERVIEW
* Type: Diploma thesis * Type: Diploma thesis
* Subject: Development of the SoftLab UserBase (SLUB) web application * Subject: Development of the SoftLab UserBase (SLUB) web application [http://artemis.cslab.ece.ntua.gr:8080/jspui/handle/123456789/17403 and https://dspace.lib.ntua.gr/xmlui/handle/123456789/50498]
* Author: Georgios Kazelidis \<giorgkazelidis@gmail.com> * Author: Georgios Kazelidis \<giorgkazelidis@gmail.com>
* Supervisor: Nikolaos Papaspyrou \<nickie@softlab.ntua.gr> * Supervisor: Nikolaos Papaspyrou \<nickie@softlab.ntua.gr>
* Copyright: © 2019 Georgios A. Kazelidis for SoftLab * Copyright: © 2019 Georgios A. Kazelidis for SoftLab
...@@ -111,7 +111,7 @@ ...@@ -111,7 +111,7 @@
&nbsp; &nbsp; &nbsp; (11) if the project database (usermergeDB) has already been created (`SHOW DATABASES;` to check), delete it: &nbsp; &nbsp; &nbsp; (11) if the project database (usermergeDB) has already been created (`SHOW DATABASES;` to check), delete it:
DROP DATABASE usermergeDB; DROP DATABASE usermergeDB;
&nbsp; &nbsp; &nbsp; (12) create the project database (no tables are created during this substep) with "utf8mb4" as the character set and X as the collation, where X is "utf8mb4_0900_ci_ai" for MySQL (server version) 8.0, "utf8mb4_unicode_520_ci" for MySQL 5.6/5.7 or "utf8mb4_unicode_ci" for MySQL 5.5: &nbsp; &nbsp; &nbsp; (12) create the project database (no tables are created during this substep) with "utf8mb4" as the character set and X as the collation, where X is "utf8mb4_0900_ai_ci" for MySQL (server version) 8.0, "utf8mb4_unicode_520_ci" for MySQL 5.6/5.7 or "utf8mb4_unicode_ci" for MySQL 5.5:
CREATE DATABASE usermergeDB CHARACTER SET utf8mb4 COLLATE X; CREATE DATABASE usermergeDB CHARACTER SET utf8mb4 COLLATE X;
&nbsp; &nbsp; &nbsp; (13) exit MySQL console: &nbsp; &nbsp; &nbsp; (13) exit MySQL console:
...@@ -275,7 +275,7 @@ with the following content (make sure to replace SERVER_IP, PROCESSES_NUMBER, TH ...@@ -275,7 +275,7 @@ with the following content (make sure to replace SERVER_IP, PROCESSES_NUMBER, TH
## LIST OF SUGGESTED TO-DO ACTIONS ## LIST OF SUGGESTED TO-DO ACTIONS
* Define a cron job that uses MySQL's `mysqldump` administrative command to regularly create project database backups (dump files) needed for recovery in case of system crashes, hardware failures, accidental data deletion, etc. [https://www.ostechnix.com/a-beginners-guide-to-cron-jobs/, https://dev.mysql.com/doc/refman/5.7/en/backup-and-recovery.html] * Define a cron job that uses MySQL's `mysqldump` administrative command to regularly create project database backups (dump files) needed for recovery in case of system crashes, hardware failures, accidental data deletion, etc. [https://www.ostechnix.com/a-beginners-guide-to-cron-jobs/, https://dev.mysql.com/doc/refman/5.7/en/backup-and-recovery.html]
* Define a cron job that uses Django's `clearsessions` administrative command to regularly clean expired sessions out of the django_session table and prevent it from growing excessively in the project database [https://www.ostechnix.com/a-beginners-guide-to-cron-jobs/, https://docs.djangoproject.com/en/2.0/topics/http/sessions/#clearing-the-session-store] * Define a cron job that uses Django's `clearsessions` administrative command to regularly clean expired sessions out of the django_session table and prevent it from growing excessively in the project database [https://www.ostechnix.com/a-beginners-guide-to-cron-jobs/, https://docs.djangoproject.com/en/2.0/topics/http/sessions/#clearing-the-session-store]
* Create and use a criteria-based (e.g. last_login-based) batch deletion view for User/Registry instances to ensure that the usermerge_user and usermerge_registry tables do not grow excessively in the project database - see models.py * Create and use an Admin-targeted view that performs bulk deletion of User/Registry instances based on specific criteria (e.g. last_login) to ensure that the usermerge_user and usermerge_registry tables do not grow excessively in the project database - see models.py
* Create and run unit tests [https://docs.djangoproject.com/en/2.0/topics/testing/] * Create and run unit tests [https://docs.djangoproject.com/en/2.0/topics/testing/]
* Make better use of the Django admin site capabilities * Make better use of the Django admin site capabilities
* Make better use of Django's model validation capabilities [https://docs.djangoproject.com/en/2.0/ref/models/instances/] * Make better use of Django's model validation capabilities [https://docs.djangoproject.com/en/2.0/ref/models/instances/]
......
...@@ -246,7 +246,7 @@ DATABASES = { ...@@ -246,7 +246,7 @@ DATABASES = {
'PORT': '', 'PORT': '',
'OPTIONS': { 'OPTIONS': {
# The charset option is set to utf8mb4 and the collation_connection variable in the init_command option is set to # The charset option is set to utf8mb4 and the collation_connection variable in the init_command option is set to
# utf8mb4_0900_ci_ai for MySQL 8.0, utf8mb4_unicode_520_ci for MySQL 5.6/5.7 or utf8mb4_unicode_ci for MySQL 5.5 # utf8mb4_0900_ai_ci for MySQL 8.0, utf8mb4_unicode_520_ci for MySQL 5.6/5.7 or utf8mb4_unicode_ci for MySQL 5.5
# in order to better support the representation and sorting/comparison of Unicode data in the database. # in order to better support the representation and sorting/comparison of Unicode data in the database.
# For more information, see # For more information, see
# https://stackoverflow.com/questions/43644218/why-is-table-charset-set-to-utf8mb4-and-collation-to-utf8mb4-unicode-520-ci?rq=1 , # https://stackoverflow.com/questions/43644218/why-is-table-charset-set-to-utf8mb4-and-collation-to-utf8mb4-unicode-520-ci?rq=1 ,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment