From c391904cf04166100f1ce66e3893ec1e56193476 Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Fri, 28 Apr 2023 17:38:27 +0200 Subject: [PATCH] docs: 1.20: cherry-pick admin/database-preparation.md * 5cb394ff2fb93935b90493894b97371734f1384e --- admin/database-preparation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/admin/database-preparation.md b/admin/database-preparation.md index 20120230..f0dcc7d7 100644 --- a/admin/database-preparation.md +++ b/admin/database-preparation.md @@ -5,7 +5,7 @@ license: 'Apache-2.0' origin_url: 'https://github.com/go-gitea/gitea/blob/e8433b7fe6dd1dfa5ecf0633568cc3e34caeb0f9/docs/content/doc/installation/database-preparation.en-us.md' --- -You need a database to use Forgejo. Forgejo supports PostgreSQL (>=10), MySQL (>=5.7) or MariaDB (>=10.0), SQLite, and MSSQL (>=2008R2 SP3). This page will guide into preparing database. Only PostgreSQL and MySQL/MariaDB will be covered here since those database engines are widely-used in production. +You need a database to use Forgejo. Forgejo supports PostgreSQL (>=10), MySQL (>=5.7) or MariaDB (>=10.0), SQLite, and MSSQL (>=2008R2 SP3). This page will guide into preparing database. Only PostgreSQL and MySQL/MariaDB will be covered here since those database engines are widely-used in production. If you plan to use SQLite, you can ignore this chapter. Database instance can be on same machine as Forgejo (local database setup), or on different machine (remote database).