EasyMDE Monaco Editor 数据库驱动： github.com/go-sql-driver/mysql github.com/lib/pq github.com/mattn/go-sqlite3 github.com/denisenkom/go-mssqldb 请访问 Awesome Gitea 获得更多的第三方集成支持 浏览器支持 技术栈 集成支持 Gitea是什么? 前，您需要准备一个数据库。Gitea 支持 PostgreSQL（>=10）、MySQL（>=5.7）、SQLite 和 MSSQL（>=2008R2 SP3）这几种数据库。本页将指导您准备数据库。由于 PostgreSQL 和 MySQL 在生产环 境中被广泛使用，因此本文档将仅涵盖这两种数据库。如果您计划使用 SQLite，则可以忽略本章内容。 数据库实例可以与 Gitea 实例在相同机器上（本地数据库），也可以与 -h example.db -p --ssl 至此应该成功连接到数据库了。 数据库准备 - 18 - 本文档使用 书栈网 · BookStack.CN 构建 所有打包的二进制程序均包含 SQLite，MySQL 和 PostgreSQL 的数据库连接支持，同时网站的静态资源均已嵌 入到可执行程序中，这一点和曾经的 Gogs 有所不同。 你可以从 下载页面 选择对应平台的二进制文件。 对于

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

3 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s also: Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)

3 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s Weblate Documentation, Release 2.4 Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = and preconfigured as follows: 4.3. Weblate deployments 41 Weblate Documentation, Release 2.4 • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

4 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)

files Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

files Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing