#### Gitea v1.21.1 中文文档  Gitea 是一个轻量级的 DevOps 平台软件。从开发计划到产品成型的整个软件生命周期，他都能够高效而轻松的帮助团队和开发者。包括 Git 托管、代码审查、团队协作、软件包注册和 CI/CD。它与 8/5/c/4/85c486ac4f4722bbd972a690837a7d17/p1_2.jpg) 下载手机APP 畅享精彩阅读 ## 目录 致谢 Gitea是什么？ 安装 对比 Gitea 与其它 Git 托管工具 数据库准备 使用二进制文件安装 使用包管理器安装 使用源代码安装 在 Linux 中以 service Docker 安装 (rootless) 使用 Docker 安装 在 Kubernetes 中安装 Gitea 在云服务器中安装 Gitea 从旧版 Gitea 升级 从 Gogs 升级 管理 Gitea 命令行 环境变量清单 备份与恢复 Email 设置 Git LFS 设置

ts/4/4/b/e/44be860493f23531759994848f32bc68/p1_1.jpg) ## Gitea ## 新一代的代码托管平台 2023.12 ## 飞致云 & 上海吉谛 2023年11月，飞致云与上海吉谛达成战略合作，获得 Gitea 企业版中国大陆地区独家代理权，向中国数字化团队交付被广泛验证、可信赖的通用工具软件。 |软件开发|软件测试|运维审计|BI分析| /4/b/e/44be860493f23531759994848f32bc68/p2_12.jpg) Star 13,400+| 上海吉谛 飞致云 1 Gitea 开源项目介绍 2 Gitea 优势总结 3 Gitea 企业版介绍 ## 代码托管平台的发展历程 · 单用户本地编辑； · 没有网络功能； · 典型产品：RCS、SCCS。 ## 阶段一 本地代码管理 阶段二 集中式代码管理 ·去中心化，稳定性和可用性增强； ·更高效的代码协同机制； ·典型产品：GitHub、GitLab、Gitea。 阶段三 分布式代码管理 基于 Git 的分布式代码托管 具备 DevSecOps 延伸能力 ## Gitea 是谁? ![Image](/uploads/documents/4/4/b/e/44be860493f23531759994848f32bc68/p5_2

USERNAME, GITLAB TOKEN, GITLAB CREDENTIALS ## Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en-us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when when selecting Version control system. ## See also Pushing changes from Weblate, GITEA USERNAME, GITEA TOKEN, GITEA CREDENTIALS ## Pagure merge requests New in version 4.3.2. This just adds a thin layer

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. #### 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS #### 1.11.5 Gitea pull requests ### New in version 4.12 This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests create pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. ## Accessing repositories USERNAME, GITLAB TOKEN, GITLAB CREDENTIALS ## Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en-us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. ## Accessing repositories USERNAME, GITLAB TOKEN, GITLAB CREDENTIALS ## Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en-us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. ## Accessing repositories USERNAME, GITLAB TOKEN, GITLAB CREDENTIALS ## Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en-us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. #### 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS #### 1.11.5 Gitea pull requests ### New in version 4.12 This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests create pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. #### 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS #### 1.11.5 Gitea pull requests ### New in version 4.12 This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests create pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

translate-toolkit 中实现对它的支持。 参见： 与翻译相关的文件格式 ### 1.11 版本控制集成 Weblate 当前支持Git（扩展支持GitHub 拉取请求、GitLab 合并请求、Gitea 拉取请求、Gerrit 及Subversion）和Mercurial 作为版本控制后端。 #### 1.11.1 访问仓库 您要使用的版本控制系统（VCS）仓库必须可供 Weblate 访问 GITLAB_CREDENTIALS #### 1.11.5 Gitea 拉取请求 ### 在 4.12 版本加入 这只是使用 Gitea API 在 Git 上添加了一个薄层，以允许将翻译更改作为拉取请求推送，而不是直接推送到仓库。 不需要使用它来访问 Git 仓库，普通的 Git 工作方式相同，唯一的区别是如何处理推送到仓库。使用 Git 将更改直接推送到仓库，而 Gitea 拉取请求创建拉取请求。 您需要在 Weblate Weblate 设置中配置 API 凭据 (GITEA_CREDENTIALS) 才能使其工作。配置完成后，您将在选择版本控制系统（VCS）时看到 Gitea 选项。 ## 参见： 推送 Weblate 的更改, GITEA_USERNAME, GITEA_TOKEN, GITEA_CREDENTIALS #### 1.11.6 Pagure 合并请求 在 4.3.2 版本加入. 这只是使用