{"id":13557218,"url":"https://github.com/bestpractical/rt","last_synced_at":"2025-05-14T14:02:15.082Z","repository":{"id":608349,"uuid":"245541","full_name":"bestpractical/rt","owner":"bestpractical","description":"Request Tracker, an enterprise-grade issue tracking system","archived":false,"fork":false,"pushed_at":"2025-05-07T20:09:26.000Z","size":195840,"stargazers_count":1020,"open_issues_count":105,"forks_count":263,"subscribers_count":69,"default_branch":"stable","last_synced_at":"2025-05-07T20:28:29.845Z","etag":null,"topics":["asset-management","bug-tracker","customer-support","helpdesk","helpdesk-ticketing","issue-management","issue-tracker","issue-tracking-system","perl","project-management","support","support-tools","ticket-management","ticketing-system","workflow"],"latest_commit_sha":null,"homepage":"https://bestpractical.com/rt","language":"Perl","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"FiloSottile/Heartbleed","license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/bestpractical.png","metadata":{"files":{"readme":"README.MariaDB","changelog":null,"contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2009-07-07T19:57:15.000Z","updated_at":"2025-05-05T13:57:48.000Z","dependencies_parsed_at":"2024-08-26T22:47:17.486Z","dependency_job_id":"5b9cbb7a-6cc9-452f-b895-254aa3615106","html_url":"https://github.com/bestpractical/rt","commit_stats":{"total_commits":21266,"total_committers":149,"mean_commits":142.7248322147651,"dds":0.793473149628515,"last_synced_commit":"93f79f2a6f946855b81190a495e97761f1ab2743"},"previous_names":[],"tags_count":727,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bestpractical%2Frt","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bestpractical%2Frt/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bestpractical%2Frt/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bestpractical%2Frt/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/bestpractical","download_url":"https://codeload.github.com/bestpractical/rt/tar.gz/refs/heads/stable","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254159140,"owners_count":22024558,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["asset-management","bug-tracker","customer-support","helpdesk","helpdesk-ticketing","issue-management","issue-tracker","issue-tracking-system","perl","project-management","support","support-tools","ticket-management","ticketing-system","workflow"],"created_at":"2024-08-01T12:04:13.238Z","updated_at":"2025-05-14T14:02:15.014Z","avatar_url":"https://github.com/bestpractical.png","language":"Perl","funding_links":[],"categories":["Perl","support"],"sub_categories":[],"readme":"DB TYPE\n-------\n\nStarting with RT 5.0.6, you must specify \"MariaDB\" as the DB type when running\n\"configure\", i.e.\n\n    ./configure --with-db-type=MariaDB\n\nThis is to install a version of DBD::mysql that still supports MariaDB.\nThe newest versions of DBD::mysql do not support MariaDB. We plan to\nswitch to \"DBD::MariaDB\" in the future when it's fully compatible\nwith RT.\n\nCHARACTER SETS\n--------------\n\nStarting with RT 5.0.0, the minimum supported MariaDB version is 10.2.5\nbecause this is the first version to provide full support for 4 byte\nutf8 characters in tables and indexes. Read on for details on this\nchange.\n\nRT 5.0.0 now defaults MariaDB tables to utf8mb4, which is available in\nversions before 10.2.5. However, before MariaDB version 10.2.5, utf8mb4\ntables could not have indexes with type VARCHAR(255): the default size\nfor index entries was 767 bytes, which is enough for 255 chars stored\nas at most 3 chars (the utf8 format), but not as 4 bytes (utf8mb4).\n10.2.5 sets the default index size to 3072 for InnoDB tables, resolving\nthat issue.\n\nhttps://mariadb.com/kb/en/changes-improvements-in-mariadb-102/\nhttps://mariadb.com/kb/en/mariadb-1025-changelog/ (search for utf8)\n\nIn MariaDB, RT uses the utf8mb4 character set to support all\nunicode characters, including the ones that are encoded with 4 bytes in\nutf8 (some Kanji characters and a good number of emojis). The DB tables\nand RT are both set to this character set.\n\nIf your MariaDB database is used only for RT, you can consider\nsetting the default character set to utf8mb4. This will\nensure that backups and other database access outside of RT have the\ncorrect character set.\n\nThis is done by adding the following lines to the MariaDB configuration:\n\n[mysqld]\ncharacter-set-server = utf8mb4\n\n[client]\ndefault-character-set = utf8mb4\n\nYou can check the values your server is using by running this command:\n    mysqladmin variables | grep -i character_set\n\nSetting the default is particularly important for mysqldump, to avoid\nbackups to be silently corrupted.\n\nIf the MySQL DB is shared with other applications and the default\ncharacter set cannot be set to utf8mb4, the command to backup the\ndatabase must set it explicitly:\n\n    ( mysqldump --default-character-set=utf8mb4 rt5 --tables sessions --no-data --single-transaction; \\\n      mysqldump --default-character-set=utf8mb4 rt5 --ignore-table rt5.sessions --single-transaction ) \\\n        | gzip \u003e rt-`date +%Y%m%d`.sql.gz\n\nRestoring a backup is done the usual way, since the character set for\nall tables is set to utf8mb4, there is no further need to tell MariaDB\nabout it:\n\n    gunzip -c rt-20191125.sql.gz | mysql -uroot -p rt5\n\nThese character set updates now allow RT on MariaDB to accept and store 4-byte\ncharacters like emojis. However, searches can still be inconsistent. You may be\nable to get different or better results by experimenting with different collation\nsettings. For more information:\n\nhttps://stackoverflow.com/a/41148052\nhttps://mariadb.com/kb/en/character-sets/\n\nTIME ZONE TABLES\n----------------\n\nCharts in RT can use time zone conversion for dates and this requires that\ntime zones are loaded into the database. MariaDB on some platforms such as\nCentos (and possibly others) have time zone tables, but they are not\npopulated and need to be loaded manually.\n\nOn Unix-like systems, you can use the mysql_tzinfo_to_sql utility, which\nuses the zoneinfo data provided on the system. Documentation on loading the\ntime zones using the mysql_tzinfo_to_sql tool can be found at:\n\nhttps://mariadb.com/kb/en/mysql_tzinfo_to_sql/\n\nYou can confirm that timezone tables are populated by running:\n\n    select CONVERT_TZ( '2020-07-27 20:00:00', 'UTC', 'Europe/London' );\n\nIf the result is \"2020-07-27 21:00:00\" the timezones are populated. If the\nresult is NULL then time zones are not populated.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbestpractical%2Frt","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbestpractical%2Frt","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbestpractical%2Frt/lists"}