0发布 Contour是基于Kubernetes的Ingress控制 器，通过将Envoy代理部署为反向代理和负载 均衡器来实现其功能。Contour提供开箱即用 的动态配置更新机制，同时保持了轻量级的配 置文件结构。此外，Contour引入全新入口 API HTTPProxy，该API通过自定义资源定义 （CRD）来实现。其主要目标是扩展Ingress API的功能，以提供更丰富的用户体验并解决

TLS 对数据库连接进行加密，以防止第三方拦截流量数据。 您需要两个有效的 TLS 证书，一个用于数据库实例（数据库服务器），一个用于 Gitea 实例（数据库客户 端）。两个证书都必须由受信任的 CA 签名。 数据库证书必须在 X509v3 Extended Key Usage 扩展属性中包含 TLS Web Server Authentication ，而客户端证 书则需要在相应的属性中包含 /path/to/postgresql.key : 数据库实例私钥 /path/to/root.crt : 用于验证客户端证书的CA证书链 2. 在 postgresql.conf 中添加以下选项： 1. ssl = on 2. ssl_ca_file = '/path/to/root.crt' 3. ssl_cert_file = '/path/to/postgresql.crt' postgresql/postgresql.crt : 数据库客户端证书 ~/.postgresql/postgresql.key : 数据库客户端私钥 ~/.postgresql/root.crt : 用于验证服务器证书的CA证书链 注意：上述文件名在 PostgreSQL 中是硬编码的，无法更改。 7. 根据需要调整凭据、所有权和权限： 1. chown git:git ~/.postgresql/postgresql

https://creativecommons.org/licenses/by-nc-sa/3.0 or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA. PREFACE BY SCOTT CHACON Welcome to the second edition of Pro Git. The first edition run git log in this project, you should get output that looks something like this: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17 log entries displayed, such as using -2 to show only the last two entries. $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17

https://creativecommons.org/licenses/by-nc- sa/3.0 or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA. 1 Preface by Scott Chacon Welcome to the second edition of Pro Git. The first edition run git log in this project, you should get output that looks something like this: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17 log entries displayed, such as using -2 to show only the last two entries. $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17

https://creativecommons.org/licenses/by-nc-sa/3.0 or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA. PREFACE BY SCOTT CHACON Welcome to the second edition of Pro Git. The first edition run git log in this project, you should get output that looks something like this: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17 log entries displayed, such as using -2 to show only the last two entries. $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17

https://creativecommons.org/licenses/by-nc-sa/3.0/deed.zh 或者写信向 Creative Commons, PO Box 1866, Mountain View, CA 94042, USA 获取。 1 Scott Chacon 序 欢迎来到 Pro Git 第二版。 第一版出版到现在已经过去了四年。 到今天，Git 虽然出现了许多改变，但是还有很 多重要的事情一如昨日。 https://github.com/schacon/simplegit-progit 当你在此项目中运行 git log 命令时，可以看到下面的输出： 43 $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17 --patch ，它会显示每次提交所引入的差异（按 补丁 的格式输出）。 你也可 以限制显示的日志条目数量，例如使用 -2 选项来只显示最近的两次提交： 44 $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17

https://creativecommons.org/licenses/by-nc-sa/3.0/deed.zh 或 者 写 信 向 Creative Commons, PO Box 1866, Mountain View, CA 94042, USA 获取。 SCOTT CHACON 序 欢迎来到 Pro Git 第二版。 第一版出版到现在已经过去了四年。 到今天，Git 虽然出现了许多改变，但是还有很多重要的事情一如昨日。 clone https://github.com/schacon/simplegit-progit 当你在此项目中运行 git log 命令时，可以看到下面的输出： $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17 --patch ，它会显示每次提交所引入的差异 （按 补丁 的格式输出）。 你也可以限制显示的日志条目数量，例如使用 -2 选项来只显示最近的两次提交： $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon Date: Mon Mar 17

(see Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the de- tails (for example on debian this can be done by placing the CA certificate into /usr/local/share/ ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the use system CA bundle instead of the one shipped with it. This can be achieved by placing following snippet to settings.py (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] =

(see Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the de- tails (for example on debian this can be done by placing the CA certificate into /usr/local/share/ ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the use system CA bundle instead of the one shipped with it. This can be achieved by placing following snippet to settings.py (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] =

(see Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the de- tails (for example on debian this can be done by placing the CA certificate into /usr/local/share/ ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the use system CA bundle instead of the one shipped with it. This can be achieved by placing following snippet to settings.py (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] =