构建 对于小型团队/项目而言，2 个 CPU 内核和 1GB 内存通常就足够了。 在 UNIX 系统上，Gitea 应使用专用的非 root 系统账户运行。 注意：Gitea 管理 ~/.ssh/authorized_keys 文件。以普通用户身份运行 Gitea 可能会破坏该用户的 登录能力。 Git 需要 2.0.0 或更高版本。 Git Large File Storage 如果启用，且 ✓ ✓ 组织里程碑 ✘ ✘ ✘ ✓ ✓ ✘ ✘ 细粒度用户角色 ✓ ✘ ✘ ✓ ✓ ✘ ✘ 提交人的身份验 证 ⁄ ✘ ? ✓ ✓ ✓ ✘ GPG 签名的提交 ✓ ✘ ✓ ✓ ✓ ✓ ✓ SSH 签名的提交 ✓ ✘ ✓ ✓ ✓ ? ? 拒绝未通过验证 的提交 ✓ ✘ ✓ ✓ ✓ ✓ ✓ 外部仓库迁移 ✓ ✘ ✓ ✓ ✓ ✓ ✓ 仓库活跃度页面 ✓ ✘ ✓ ✓ ✓ ✓ ✓ 分支管理 ✓ ，以将所有钩子更新为包含新的二进制文件路径。请注意，这将覆盖所有 Git 钩子，包括自定义的钩 子。 如果您没有使用 Gitea 内置的 SSH 服务器，您还需要通过在管理选项中运行任务 Update the '.ssh/authorized_keys' file with Gitea SSH keys. 来重新编写授权密钥文件。 更多经验总结，请参考英文版 Troubleshooting 如果从本页中没有找到你需要的内容，请访问

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Generating Your SSH Public Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . protocol for Git network transactions. Most of the examples in the book have been changed to HTTP from SSH because it’s so much simpler. It’s been amazing to watch Git grow over the past few years from a relatively the https:// protocol, but you may also see git:// or user@server:path/to/repo.git, which uses the SSH transfer protocol. Getting Git on a Server will introduce all of the available options the server

Protocol The HTTP Protocols The SSH Protocol The Git Protocol Getting Git on a Server Putting the Bare Repository on a Server Small Setups Generating Your SSH Public Key Setting Up the Server Build Number Preparing a Release The Shortlog Summary GitHub Account Setup and Configuration SSH Access Your Avatar Your Email Addresses Two Factor Authentication Contributing to a Project Forking protocol for Git network transactions. Most of the examples in the book have been changed to HTTP from SSH because it’s so much simpler. It’s been amazing to watch Git grow over the past few years from a

Protocol The HTTP Protocols The SSH Protocol The Git Protocol Getting Git on a Server Putting the Bare Repository on a Server Small Setups Generating Your SSH Public Key Setting Up the Server Build Number Preparing a Release The Shortlog Summary GitHub Account Setup and Configuration SSH Access Your Avatar Your Email Addresses Two Factor Authentication Contributing to a Project Forking protocol for Git network transactions. Most of the examples in the book have been changed to HTTP from SSH because it’s so much simpler. It’s been amazing to watch Git grow over the past few years from a

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 生成 SSH 公钥 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 将会帮助你加入到一个巨大的社区中。不论你决定为自己的代码使用哪一个 Git 托管服务，这都很有价值。 自从上次出版以来另一个重大变革是 Git 网络传输 HTTP 协议的开发与崛起。书中的大多数例子都已经从 SSH 切换到 HTTP，因为它更简单。 在过去这几年看到 Git 从一个相对无名的版本管理系统成长为商业与开源版本管理的事实标准是令人吃惊的。我 很高兴 Pro Git 做得很好并已经成为市场上几本既成功又完全开源的技术书籍之一。 协议 @wych42 @Geno1024 王波 @xinqiu @morefreeze 4.2 在服务器上搭建 Git @neo1218 @Geno1024 王波 @xinqiu 4.3 生成 SSH 公钥 @oranzhang @secondwtq @IceNature @jeffsui 4.4 配置服务器 @oranzhang @Geno1024 @IceNature @secondwtq

变基的基本操作 更有趣的变基例子 变基的风险 用变基解决变基 变基 vs. 合并 总结 服务器上的 Git 协议 本地协议 HTTP 协议 SSH 协议 Git 协议 在服务器上搭建 Git 把裸仓库放到服务器上 小型安装 生成 SSH 公钥 配置服务器 Git 守护进程 Smart HTTP GitWeb GitLab 安装 管理 基本用途 一起工作 第三方托管的选择 应用来自邮件的补丁 检出远程分支 确定引入了哪些东西 将贡献的工作整合进来 为发布打标签 生成一个构建号 准备一次发布 制作提交简报 总结 GitHub 账户的创建和配置 SSH 访问 头像 邮件地址 两步验证 对项目做出贡献 派生项目 GitHub 流程 拉取请求的进阶用法 GitHub 风格的 Markdown 让你的 GitHub 公共仓库保持更新 将会帮助你加入到一个巨大的社区中。不论你决定为自己 的代码使用哪一个 Git 托管服务，这都很有价值。 自从上次出版以来另一个重大变革是 Git 网络传输 HTTP 协议的开发与崛起。 书中的大多数例子都已经从 SSH 切换到 HTTP，因为它更简单。 在过去这几年看到 Git 从一个相对无名的版本管理系统成长为商业与开源版本 管理的事实标准是令人吃惊的。我很高兴 Pro Git 做得很好并已经成为市场上 几本既成功又完全开源的技术书籍之一。

The Weblate Manual, Release 4.13 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.12.2 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

The Weblate Manual, Release 4.13.1 How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public

localization, Avoiding merge conflicts How to access repositories over SSH? Please see Accessing repositories for info on setting up SSH keys. How to fix merge conflicts in translations? Merge conflicts repository, it lives under the DATA_DIR directory and is named vcs/ //. If you have SSH access to this machine, you can use the repository directly. For anonymous access, you might want push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used method to access private repositories is based on SSH. Authorize the public