From c4b88cb28e0b8c03cf0406d21383b617319da8df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Dachary?= Date: Wed, 20 Jul 2022 09:58:13 +0000 Subject: [PATCH] new deploy: 2022-07-20T09:58:13+00:00 --- blog/1-17-breaking-episode-2/index.html | 328 ++++++++++++++++++++++++ blog/atom.xml | 30 ++- blog/index.html | 37 +++ search_index.en.js | 2 +- sitemap.xml | 4 + tags/gitea/atom.xml | 30 ++- tags/gitea/index.html | 28 ++ tags/hostea/atom.xml | 30 ++- tags/hostea/index.html | 28 ++ tags/index.html | 10 +- tags/problem/atom.xml | 30 ++- tags/problem/index.html | 28 ++ tags/troubleshoot/atom.xml | 30 ++- tags/troubleshoot/index.html | 28 ++ tags/tutorial/atom.xml | 30 ++- tags/tutorial/index.html | 28 ++ 16 files changed, 689 insertions(+), 12 deletions(-) create mode 100644 blog/1-17-breaking-episode-2/index.html diff --git a/blog/1-17-breaking-episode-2/index.html b/blog/1-17-breaking-episode-2/index.html new file mode 100644 index 0000000..93a68c4 --- /dev/null +++ b/blog/1-17-breaking-episode-2/index.html @@ -0,0 +1,328 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + 1.17 breaking changes episode 2: preserving a custom gitconfig | Hostea: Managed Gitea Hosting + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +
+
+ + +
+

1.17 breaking changes episode 2: preserving a custom gitconfig

+ + + +
+

On June 21st, 2022 1.17.0-rc1 was published and the location of the gitconfig file moved to a new location, which required manual intervention. This change impacted a large number of Gitea installations because the docker image tag latest was set to 1.17.0-rc1 by accident. As a result, about 10,000 pulls per hour from the docker hub got the release candidate instead of the expected stable version.

+

Unfortunately moving the git home directory in 1.17.0-rc1 was implemented in way that created a security problem. The fix that was merged in Gitea to fix it requires moving the gitconfig file and was released July 19th, 2022 in 1.17.0-rc2.

+

This would have been a minor inconvenience if it only has an impact on adventurous people trying the release candidate in a test environment. But since all Gitea production installations based on the latest tag were inadvertently upgraded to 1.17.0-rc1, the admins who moved their custom .gitconfig will need to move it one more time when upgrading to 1.17.0-rc2.

+

In 1.17.0-rc2, a custom .gitconfig must be moved manually to the new git home directory as follows:

+ +
$ gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor 
+[1] Check paths and basic configuration
+ - [I] Configuration File Path:    "/data/gitea/conf/app.ini"
+ - [I] Repository Root Path:       "/data/git/repositories"
+ - [I] Data Root Path:             "/data/gitea"
+ - [I] Custom File Root Path:      "/data/gitea"
+ - [I] Work directory:             "/app/gitea"
+ - [I] Log Root Path:              "/data/gitea/log"
+OK
+
+
    +
  • Copy the $HOME/.gitconfig file to the Data Root Path/home (which is /data/gitea/home in the example above).
  • +
+ +
+
+
+ + +
+ + +
+ + +
+ + diff --git a/blog/atom.xml b/blog/atom.xml index f1592c1..bdf1467 100644 --- a/blog/atom.xml +++ b/blog/atom.xml @@ -4,8 +4,36 @@ Zola - 2022-07-10T00:00:00+00:00 + 2022-07-20T00:00:00+00:00 https://hostea.org/blog/atom.xml + + 1.17 breaking changes episode 2: preserving a custom gitconfig + 2022-07-20T00:00:00+00:00 + 2022-07-20T00:00:00+00:00 + + https://hostea.org/blog/1-17-breaking-episode-2/ + <p>On June 21st, 2022 1.17.0-rc1 was published and the location of the gitconfig file moved to a new location, <a href="2022-06-23-1.17-breaking-episode-1">which required manual intervention</a>. This change impacted a large number of Gitea installations because the docker image tag <strong>latest</strong> <a href="https://mastodon.online/@hostea/108514134565401798">was set to 1.17.0-rc1</a> by accident. As a result, about 10,000 pulls per hour from the docker hub got the release candidate instead of the expected stable version.</p> +<p>Unfortunately moving the git home directory in 1.17.0-rc1 was implemented in way that created a security problem. The <a href="https://github.com/go-gitea/gitea/pull/20114">fix that was merged in Gitea</a> to fix it requires moving the gitconfig file and was released July 19th, 2022 in 1.17.0-rc2.</p> +<p>This would have been a minor inconvenience if it only has an impact on adventurous people trying the release candidate in a test environment. But since all Gitea production installations based on the <strong>latest</strong> tag were inadvertently upgraded to 1.17.0-rc1, the admins who moved their custom .gitconfig will need to move it one more time when upgrading to 1.17.0-rc2.</p> +<p>In 1.17.0-rc2, a custom .gitconfig must be moved manually to the <a href="https://docs.gitea.io/en-us/config-cheat-sheet/#git-git">new git home directory</a> as follows:</p> +<ul> +<li>Figure out the directory where <code>$HOME/.gitconfig</code> must be moved by <a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/">running the doctor</a>:</li> +</ul> +<pre data-lang="shell" style="background-color:#2b303b;color:#c0c5ce;" class="language-shell "><code class="language-shell" data-lang="shell"><span>$ gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor +</span><span>[1] Check paths and basic configuration +</span><span> - [I] Configuration File Path: &quot;/data/gitea/conf/app.ini&quot; +</span><span> - [I] Repository Root Path: &quot;/data/git/repositories&quot; +</span><span> - [I] Data Root Path: &quot;/data/gitea&quot; +</span><span> - [I] Custom File Root Path: &quot;/data/gitea&quot; +</span><span> - [I] Work directory: &quot;/app/gitea&quot; +</span><span> - [I] Log Root Path: &quot;/data/gitea/log&quot; +</span><span>OK +</span></code></pre> +<ul> +<li>Copy the <code>$HOME/.gitconfig</code> file to the <strong>Data Root Path</strong>/home (which is <code>/data/gitea/home</code> in the example above).</li> +</ul> + + Get a Gitea instance with CI at Hostea 2022-07-10T00:00:00+00:00 diff --git a/blog/index.html b/blog/index.html index c2600dd..8c026ad 100644 --- a/blog/index.html +++ b/blog/index.html @@ -211,6 +211,43 @@