all you have to do is put a bare Git repository under your HTTP document root and set up a specific post-update hook, and you’re done (see Git Hooks). At that point, anyone who can access the web server /path/to/git_project gitproject.git $ cd gitproject.git $ mv hooks/post-update.sample hooks/post-update $ chmod a+x hooks/post-update That’s all. The post-update hook that comes with Git by default runs the appropriate hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your Git

all you have to do is put a bare Git repository under your HTTP document root and set up a specific post-update hook, and you’re done (see Git Hooks). At that point, anyone who can access the web server /path/to/git_project gitproject.git $ cd gitproject.git $ mv hooks/post-update.sample hooks/post-update $ chmod a+x hooks/post-update That’s all. The post-update hook that comes with Git by default runs the appropriate hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your Git

all you have to do is put a bare Git repository under your HTTP document root and set up a specific post-update hook, and you’re done (see Git Hooks). At that point, anyone who can access the web server /path/to/git_project gitproject.git $ cd gitproject.git $ mv hooks/post-update.sample hooks/post-update $ chmod a+x hooks/post-update That’s all. The post-update hook that comes with Git by default runs the appropriate hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your Git

HTTP 协 议里 web 服务器仅把裸版本库当作普通文件来对待，提供文件服务。 哑 HTTP 协议的优美之处在于设置起来简 单。 基本上，只需要把一个裸版本库放在 HTTP 根目录，设置一个叫做 post-update 的挂钩就可以了 （见 Git 钩子）。 此时，只要能访问 web 服务器上你的版本库，就可以克隆你的版本库。 下面是设置从 HTTP 访问版本 库的方法： $ cd /var/www/htdocs/ /path/to/git_project gitproject.git $ cd gitproject.git $ mv hooks/post-update.sample hooks/post-update $ chmod a+x hooks/post-update 这样就可以了。 Git 自带的 post-update 挂钩会默认执行合适的命令（git update-server-info），来 确保通过 HTTP tonychacon/fade List-Archive: https://github.com/tonychacon/fade List-Post: List-Unsubscribe: ，.

错误信息中的 [...] 部分将包含您先前 Gitea 二进制文件的路径。 要解决此问题，请转到管理选项，并运行任务 Resynchronize pre-receive, update and post-receive hooks of all repositories ，以将所有钩子更新为包含新的二进制文件路径。请注意，这将覆盖所有 Git 钩子，包括自定义的钩 子。 如果您没有使用 Gitea 允许请求的协议 ALLOW_DOMAIN : *: 允许请求的域名列表 ALLOW_SUBDOMAIN : false: 允许上述列出的头部的子域名发出请求。 METHODS : GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS: 允许发起的请求方式列表 MAX_AGE : 10m: 缓存响应的最大时间 ALLOW_CREDENTIALS : false: 允许带有凭据的请求 密钥更新 ‘.ssh/authorized_keys’ 文件 ( cron.resync_all_sshkeys ) Cron - 重新同步所有仓库的 pre-receive、update 和 post-receive 钩 子 ( cron.resync_all_hooks ) Cron - 重新初始化所有缺失的 Git 仓库，但记录已存在 ( cron.reinit_missing_repos

HTTP 协议里 web 服务器仅把裸版本库当作普通文件来 对待，提供文件服务。 哑 HTTP 协议的优美之处在于设置起来简单。 基本 上，只需要把一个裸版本库放在 HTTP 根目录，设置一个叫做 post-update 的 挂钩就可以了 （见 Git 钩子）。 此时，只要能访问 web 服务器上你的版本 库，就可以克隆你的版本库。 下面是设置从 HTTP 访问版本库的方法： $ cd /var/www/htdocs/ /path/to/git_project gitproject.git $ cd gitproject.git $ mv hooks/post-update.sample hooks/post-update $ chmod a+x hooks/post-update 这样就可以了。 Git 自带的 post-update 挂钩会默认执行合适的命令（git update-server-info），来确保通过 HTTP tonychacon/fade List-Archive: https://github.com/tonychacon/fade List-Post: List-Unsubscribe: ，.