0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-12-24 22:32:43 -05:00

docs: 1.20: cherry-pick admin/database-preparation.md

* 5cb394ff2fb93935b90493894b97371734f1384e
This commit is contained in:
Earl Warren 2023-04-28 17:38:27 +02:00 committed by Caesar Schinas
parent c676a0b8ce
commit c391904cf0
No known key found for this signature in database
GPG key ID: AE9108461BEA5ACF

View file

@ -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' 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). Database instance can be on same machine as Forgejo (local database setup), or on different machine (remote database).