oppi.li / perf-test
loading up the forgejo repo on tangled to test page performance
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Update database-preparation and add note re: MariaDB (#27232)

update DB docs per feedback.
https://gitea.com/gitea/gitea-docusaurus/issues/69

authored by

techknowlogick and committed by
GitHub 0816463c 2325fe77

+3 -3
+3 -3
docs/content/installation/database-preparation.en-us.md
··· 17 17 18 18 # Database Preparation 19 19 20 - You need a database to use Gitea. Gitea supports PostgreSQL (>=10), MySQL (>=5.7), SQLite, and MSSQL (>=2008R2 SP3). This page will guide into preparing database. Only PostgreSQL and MySQL will be covered here since those database engines are widely-used in production. If you plan to use SQLite, you can ignore this chapter. 20 + You need a database to use Gitea. Gitea supports PostgreSQL (>=10), MySQL (>=5.7), MariaDB, SQLite, and MSSQL (>=2008R2 SP3). This page will guide into preparing database. Only PostgreSQL and MySQL will be covered here since those database engines are widely-used in production. If you plan to use SQLite, you can ignore this chapter. 21 21 22 22 Database instance can be on same machine as Gitea (local database setup), or on different machine (remote database). 23 23 24 24 Note: All steps below requires that the database engine of your choice is installed on your system. For remote database setup, install the server application on database instance and client program on your Gitea server. The client program is used to test connection to the database from Gitea server, while Gitea itself use database driver provided by Go to accomplish the same thing. In addition, make sure you use same engine version for both server and client for some engine features to work. For security reason, protect `root` (MySQL) or `postgres` (PostgreSQL) database superuser with secure password. The steps assumes that you run Linux for both database and Gitea servers. 25 25 26 - ## MySQL 26 + ## MySQL/MariaDB 27 27 28 28 1. For remote database setup, you will need to make MySQL listen to your IP address. Edit `bind-address` option on `/etc/mysql/my.cnf` on database instance to: 29 29 ··· 45 45 46 46 ```sql 47 47 SET old_passwords=0; 48 - CREATE USER 'gitea' IDENTIFIED BY 'gitea'; 48 + CREATE USER 'gitea'@'%' IDENTIFIED BY 'gitea'; 49 49 ``` 50 50 51 51 For remote database: