new deploy: 2022-06-23T17:04:20+00:00
dachary
parent
fe419d5bd5
commit
86c6ef41f9
|
|
@ -0,0 +1,328 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8" />
|
||||
<meta name="viewport" content="width=device-width" />
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
|
||||
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png" />
|
||||
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png" />
|
||||
<link rel="manifest" href="/site.webmanifest" />
|
||||
<link rel="stylesheet" href="https://hostea.org/main.css" />
|
||||
<link
|
||||
rel="stylesheet"
|
||||
media="screen and (max-width: 1300px)"
|
||||
href="https://hostea.org/mobile.css"
|
||||
/>
|
||||
|
||||
<meta name="referrer" content="no-referrer-when-downgrade" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="https://hostea.org/main.css" />
|
||||
<link
|
||||
rel="stylesheet"
|
||||
media="screen and (max-width: 1300px)"
|
||||
href="https://hostea.org/mobile.css"
|
||||
/>
|
||||
|
||||
<meta name="referrer" content="no-referrer-when-downgrade" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig | Hostea: Managed Gitea Hosting </title>
|
||||
<meta name="referrer" content="no-referrer-when-downgrade" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
|
||||
<meta name="description" content="The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well." />
|
||||
|
||||
|
||||
<meta property="og:title" content="1.17 breaking changes episode 1: preserving a custom gitconfig | Hostea: Managed Gitea Hosting " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://hostea.org" />
|
||||
|
||||
<meta property="og:description" content="The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well." />
|
||||
<meta
|
||||
property="og:site_name"
|
||||
content="1.17 breaking changes episode 1: preserving a custom gitconfig | Hostea: Managed Gitea Hosting "
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="57x57"
|
||||
href="https://hostea.org/apple-icon-57x57.png?h=c21de14cfdf862a6472ae977557fa048a7c36d39337e61d3274705e9bd8e857f"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="60x60"
|
||||
href="https://hostea.org/apple-icon-60x60.png?h=67089d9025a52d0d1ddce450078c7acefe2c150a2427dec9f5e13c6314f74281"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="72x72"
|
||||
href="https://hostea.org/apple-icon-72x72.png?h=70725943de8884804f9da28202ced0ad6fed483ae9cf8f6d874aa133e30cb693"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="76x76"
|
||||
href="https://hostea.org/apple-icon-76x76.png?h=1e6e8072df3b21bdcea254a42aac6e993611e845f91ddd79f6f35a6c441710a5"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="114x114"
|
||||
href="https://hostea.org/apple-icon-114x114.png?h=c20099f8190ed3962fab5726c5594857a871cdb3ee98439343c622cd3727fed6"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="120x120"
|
||||
href="https://hostea.org/apple-icon-120x120.png?h=4df78e402e60b58c6d44764678bdd737b5b6a836aeb85fb75fa49f706f7e8c81"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="144x144"
|
||||
href="https://hostea.org/apple-icon-144x144.png?h=0c44e6655d714f89ee95cc151032d1f0dc3204bd24d1ca2ee9d94692d4ede84d"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="152x152"
|
||||
href="https://hostea.org/apple-icon-152x152.png?h=157918f883ff95d4eeb6452d0ebb61ca5e21ea0dcac1aefe825f3e2f3999052f"
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
sizes="180x180"
|
||||
href="https://hostea.org/apple-icon-180x180.png?h=7d5c16d379b7db6d8ea5aae64921d7162b84f543763acd8fc7c107f80a600213"
|
||||
/>
|
||||
<link
|
||||
rel="icon"
|
||||
type="image/png"
|
||||
sizes="192x192"
|
||||
href="https://hostea.org/android-icon-192x192.png?h=095e3835b082dba07f606c33fa6f71bcd671a71e987b0ab2e46dcddceef52b9c"
|
||||
/>
|
||||
<link
|
||||
rel="icon"
|
||||
type="image/png"
|
||||
sizes="32x32"
|
||||
href="https://hostea.org/favicon-32x32.png?h=d7cd5d6390d58e729cd1f3564add60e9d8b63f54482a7f4cb5a66bb4780dfb05"
|
||||
/>
|
||||
<link
|
||||
rel="icon"
|
||||
type="image/png"
|
||||
sizes="96x96"
|
||||
href="https://hostea.org/favicon-96x96.png?h=5e01ce966b1d7ed88e0b01226d74ad8aaa65cea839073eb1ec6e115e76f3b2db"
|
||||
/>
|
||||
<link
|
||||
rel="icon"
|
||||
type="image/png"
|
||||
sizes="16x16"
|
||||
href="https://hostea.org/favicon-16x16.png?h=442e55b5177a8b501f75401b6b61bddace8d1ef8d91dab611fb1993293682ba5"
|
||||
/>
|
||||
<link
|
||||
rel="manifest"
|
||||
href="https://hostea.org/manifest.json?h=27eca3e8297eb7ff340deb3849b210185a459b3845456aa4d0036f6d966b3518"
|
||||
/>
|
||||
<meta name="msapplication-TileColor" content="#ffffff" />
|
||||
<meta
|
||||
name="msapplication-TileImage"
|
||||
content="https://hostea.org/ms-icon-144x144.png?h=8170ab51b871b84b8f98bd03cf441afdffb2998b7dfffb04abb7ebf5deeb1f94"
|
||||
/>
|
||||
<meta name="theme-color" content="#ffffff" />
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
|
||||
|
||||
|
||||
</head>
|
||||
<body class="base">
|
||||
<header>
|
||||
<nav class="nav__container">
|
||||
<input type="checkbox" class="nav__toggle" id="nav__toggle" />
|
||||
|
||||
<div class="nav__header">
|
||||
<a class="nav__logo-container" href="/">
|
||||
|
||||
<img src="https://hostea.org/android-icon-48x48.png?h=5115cfa26ec433a1f436236b2842c138d9d17f0c5a6376e3102c14e949dae1cb"
|
||||
alt="Hostea temporary logo"/>
|
||||
<p class="nav__home-btn">
|
||||
ostea
|
||||
</p>
|
||||
</a>
|
||||
<label class="nav__hamburger-menu" for="nav__toggle">
|
||||
<span class="nav__hamburger-inner"></span>
|
||||
</label>
|
||||
</div>
|
||||
|
||||
<div class="nav__spacer"></div>
|
||||
|
||||
<div class="nav__link-group">
|
||||
|
||||
|
||||
|
||||
<div class="nav__link-container">
|
||||
<a class="nav__link" rel="noreferrer" href="/about/">About</a>
|
||||
</div>
|
||||
|
||||
|
||||
<div class="nav__link-container">
|
||||
<a class="nav__link" rel="noreferrer" href="/blog/">Blog</a>
|
||||
</div>
|
||||
|
||||
|
||||
<div class="nav__link-container">
|
||||
<a class="nav__link" rel="noreferrer" href="/contact/">Contact</a>
|
||||
</div>
|
||||
|
||||
|
||||
<div class="nav__link-container">
|
||||
<a class="nav__link" rel="noreferrer" href="/gitea-clinic/">Gitea Clinic</a>
|
||||
</div>
|
||||
|
||||
|
||||
<div class="nav__link-container">
|
||||
<a class="nav__link" rel="noreferrer" href="/talks/">Talks</a>
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</header>
|
||||
<!-- See ../sass/main.scss. Required for pushing footer to the very
|
||||
bottom of the page -->
|
||||
<div class="main__content-container">
|
||||
<main>
|
||||
|
||||
|
||||
<div class="page__container">
|
||||
<h1 class="page__group-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h1>
|
||||
<p class="blog__post-meta">
|
||||
|
||||
|
||||
|
||||
<a href="https://dachary.org" class="post__author">Loïc Dachary</a>
|
||||
|
||||
|
||||
|
||||
|
||||
· 22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
|
||||
<div class="blog__content">
|
||||
<p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea >= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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: "/data/gitea/conf/app.ini"
|
||||
</span><span> - [I] Repository Root Path: "/data/git/repositories"
|
||||
</span><span> - [I] Data Root Path: "/data/gitea"
|
||||
</span><span> - [I] Custom File Root Path: "/data/gitea"
|
||||
</span><span> - [I] Work directory: "/app/gitea"
|
||||
</span><span> - [I] Log Root Path: "/data/gitea/log"
|
||||
</span><span>OK
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>Copy the <code>$HOME/.gitconfig</code> file to the <strong>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
|
||||
</div>
|
||||
<br>
|
||||
<br>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer__container">
|
||||
<!-- <div class="footer__column"> --->
|
||||
<p class="footer__column license__conatiner">
|
||||
All text <a
|
||||
class="license__link"
|
||||
rel="noreferrer"
|
||||
href="http://creativecommons.org/licenses/by-sa/4.0/"
|
||||
target="_blank"
|
||||
> CC-BY-SA </a
|
||||
>
|
||||
& code
|
||||
<a
|
||||
class="license__link"
|
||||
rel="noreferrer"
|
||||
href="https://www.gnu.org/licenses/agpl-3.0.en.html"
|
||||
target="_blank"
|
||||
> AGPL </a
|
||||
>
|
||||
|
|
||||
<a
|
||||
class="license__link"
|
||||
rel="noreferrer"
|
||||
href="https://www.eff.org/issues/do-not-track/amp/"
|
||||
target="_blank"
|
||||
> No AMP </a
|
||||
>
|
||||
</p>
|
||||
<!-- </div> -->
|
||||
<div class="footer__column--center">
|
||||
<a href="/blog/atom.xml" target="_blank" rel="noopener" title="RSS">
|
||||
<img
|
||||
src="https://hostea.org/icons/rss.svg?h=f6cd584bdbcd2eb4d1b8b84c9cf083ef45f772167c33fdcee754b35ae8ff4c7d"
|
||||
class="footer__icon"
|
||||
alt="Email icon"
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
<div class="footer__column">
|
||||
<a href="/about" title="About">About</a>
|
||||
<a href="/coc" title="Code of Conduct">CoC</a>
|
||||
<span class="footer__column-divider--mobile-only">|</span>
|
||||
<a href="/legalese" title="Legalese">Legalese</a>
|
||||
<a href="/privacy-policy" title="Privacy Policy">Privacy</a>
|
||||
<span class="footer__column-divider--mobile-only">|</span>
|
||||
<a
|
||||
href="https://stats.uptimerobot.com/EQ7VJHWylx"
|
||||
rel="noreferrer"
|
||||
target="_blank"
|
||||
title="Status"
|
||||
>Status</a
|
||||
>
|
||||
<a href="/tos" title="Terms of Service">ToS</a>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -4,8 +4,44 @@
|
|||
<link href="https://hostea.org/blog/atom.xml" rel="self" type="application/atom+xml"/>
|
||||
<link href="https://hostea.org/blog/"/>
|
||||
<generator uri="https://www.getzola.org/">Zola</generator>
|
||||
<updated>2022-06-14T00:00:00+00:00</updated>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<id>https://hostea.org/blog/atom.xml</id>
|
||||
<entry xml:lang="en">
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig</title>
|
||||
<published>2022-06-22T00:00:00+00:00</published>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/1-17-breaking-episode-1/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/1-17-breaking-episode-1/</id>
|
||||
<content type="html"><p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea &gt;= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>[tutorial] A gentle introduction to the gitea doctor</title>
|
||||
<published>2022-06-14T00:00:00+00:00</published>
|
||||
|
|
|
|||
|
|
@ -203,6 +203,43 @@
|
|||
|
||||
<ul class="blog__list">
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/1-17-breaking-episode-1/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h2>
|
||||
<p class="blog__post-meta">
|
||||
|
||||
|
||||
|
||||
<a href="https://dachary.org" class="post__author">Loïc Dachary</a>
|
||||
|
||||
|
||||
|
||||
|
||||
· 22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
|
||||
<p class="blog__post-description">The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well. </p>
|
||||
</a>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[tutorial] A gentle introduction to the gitea doctor</h2>
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -9,6 +9,10 @@
|
|||
<url>
|
||||
<loc>https://hostea.org/blog/</loc>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://hostea.org/blog/1-17-breaking-episode-1/</loc>
|
||||
<lastmod>2022-06-22</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://hostea.org/blog/blank-or-error-500-page-after-login/</loc>
|
||||
<lastmod>2022-05-08</lastmod>
|
||||
|
|
|
|||
|
|
@ -4,8 +4,44 @@
|
|||
<link href="https://hostea.org/tags/gitea/atom.xml" rel="self" type="application/atom+xml"/>
|
||||
<link href="https://hostea.org"/>
|
||||
<generator uri="https://www.getzola.org/">Zola</generator>
|
||||
<updated>2022-06-14T00:00:00+00:00</updated>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<id>https://hostea.org/tags/gitea/atom.xml</id>
|
||||
<entry xml:lang="en">
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig</title>
|
||||
<published>2022-06-22T00:00:00+00:00</published>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/1-17-breaking-episode-1/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/1-17-breaking-episode-1/</id>
|
||||
<content type="html"><p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea &gt;= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>[tutorial] A gentle introduction to the gitea doctor</title>
|
||||
<published>2022-06-14T00:00:00+00:00</published>
|
||||
|
|
|
|||
|
|
@ -209,6 +209,34 @@
|
|||
</a></div>
|
||||
<ul class="blog__list">
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/1-17-breaking-episode-1/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h2>
|
||||
<p class="blog__post-meta">
|
||||
22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
<p class="blog__post-description">The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well. </p>
|
||||
</a>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[tutorial] A gentle introduction to the gitea doctor</h2>
|
||||
|
|
|
|||
|
|
@ -4,8 +4,44 @@
|
|||
<link href="https://hostea.org/tags/hostea/atom.xml" rel="self" type="application/atom+xml"/>
|
||||
<link href="https://hostea.org"/>
|
||||
<generator uri="https://www.getzola.org/">Zola</generator>
|
||||
<updated>2022-06-14T00:00:00+00:00</updated>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<id>https://hostea.org/tags/hostea/atom.xml</id>
|
||||
<entry xml:lang="en">
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig</title>
|
||||
<published>2022-06-22T00:00:00+00:00</published>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/1-17-breaking-episode-1/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/1-17-breaking-episode-1/</id>
|
||||
<content type="html"><p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea &gt;= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>[tutorial] A gentle introduction to the gitea doctor</title>
|
||||
<published>2022-06-14T00:00:00+00:00</published>
|
||||
|
|
|
|||
|
|
@ -209,6 +209,34 @@
|
|||
</a></div>
|
||||
<ul class="blog__list">
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/1-17-breaking-episode-1/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h2>
|
||||
<p class="blog__post-meta">
|
||||
22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
<p class="blog__post-description">The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well. </p>
|
||||
</a>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[tutorial] A gentle introduction to the gitea doctor</h2>
|
||||
|
|
|
|||
|
|
@ -269,7 +269,7 @@
|
|||
|
||||
|
||||
|
||||
<span class="tag__meta">7 entries</span>
|
||||
<span class="tag__meta">8 entries</span>
|
||||
</a>
|
||||
<a class="tag__rss-link" href="https://hostea.org/tags/gitea/atom.xml" target="_blank" rel="noopener" title="RSS">
|
||||
<img
|
||||
|
|
@ -287,7 +287,7 @@
|
|||
|
||||
|
||||
|
||||
<span class="tag__meta">8 entries</span>
|
||||
<span class="tag__meta">9 entries</span>
|
||||
</a>
|
||||
<a class="tag__rss-link" href="https://hostea.org/tags/hostea/atom.xml" target="_blank" rel="noopener" title="RSS">
|
||||
<img
|
||||
|
|
@ -305,7 +305,7 @@
|
|||
|
||||
|
||||
|
||||
<span class="tag__meta">6 entries</span>
|
||||
<span class="tag__meta">7 entries</span>
|
||||
</a>
|
||||
<a class="tag__rss-link" href="https://hostea.org/tags/problem/atom.xml" target="_blank" rel="noopener" title="RSS">
|
||||
<img
|
||||
|
|
@ -323,7 +323,7 @@
|
|||
|
||||
|
||||
|
||||
<span class="tag__meta">6 entries</span>
|
||||
<span class="tag__meta">7 entries</span>
|
||||
</a>
|
||||
<a class="tag__rss-link" href="https://hostea.org/tags/troubleshoot/atom.xml" target="_blank" rel="noopener" title="RSS">
|
||||
<img
|
||||
|
|
@ -341,9 +341,7 @@
|
|||
|
||||
|
||||
|
||||
|
||||
|
||||
<span class="tag__meta">1 entry</span>
|
||||
<span class="tag__meta">2 entries</span>
|
||||
</a>
|
||||
<a class="tag__rss-link" href="https://hostea.org/tags/tutorial/atom.xml" target="_blank" rel="noopener" title="RSS">
|
||||
<img
|
||||
|
|
|
|||
|
|
@ -4,8 +4,44 @@
|
|||
<link href="https://hostea.org/tags/problem/atom.xml" rel="self" type="application/atom+xml"/>
|
||||
<link href="https://hostea.org"/>
|
||||
<generator uri="https://www.getzola.org/">Zola</generator>
|
||||
<updated>2022-06-14T00:00:00+00:00</updated>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<id>https://hostea.org/tags/problem/atom.xml</id>
|
||||
<entry xml:lang="en">
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig</title>
|
||||
<published>2022-06-22T00:00:00+00:00</published>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/1-17-breaking-episode-1/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/1-17-breaking-episode-1/</id>
|
||||
<content type="html"><p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea &gt;= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>[tutorial] A gentle introduction to the gitea doctor</title>
|
||||
<published>2022-06-14T00:00:00+00:00</published>
|
||||
|
|
|
|||
|
|
@ -209,6 +209,34 @@
|
|||
</a></div>
|
||||
<ul class="blog__list">
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/1-17-breaking-episode-1/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h2>
|
||||
<p class="blog__post-meta">
|
||||
22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
<p class="blog__post-description">The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well. </p>
|
||||
</a>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[tutorial] A gentle introduction to the gitea doctor</h2>
|
||||
|
|
|
|||
|
|
@ -4,8 +4,44 @@
|
|||
<link href="https://hostea.org/tags/troubleshoot/atom.xml" rel="self" type="application/atom+xml"/>
|
||||
<link href="https://hostea.org"/>
|
||||
<generator uri="https://www.getzola.org/">Zola</generator>
|
||||
<updated>2022-06-14T00:00:00+00:00</updated>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<id>https://hostea.org/tags/troubleshoot/atom.xml</id>
|
||||
<entry xml:lang="en">
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig</title>
|
||||
<published>2022-06-22T00:00:00+00:00</published>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/1-17-breaking-episode-1/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/1-17-breaking-episode-1/</id>
|
||||
<content type="html"><p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea &gt;= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>[tutorial] A gentle introduction to the gitea doctor</title>
|
||||
<published>2022-06-14T00:00:00+00:00</published>
|
||||
|
|
|
|||
|
|
@ -209,6 +209,34 @@
|
|||
</a></div>
|
||||
<ul class="blog__list">
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/1-17-breaking-episode-1/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h2>
|
||||
<p class="blog__post-meta">
|
||||
22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
<p class="blog__post-description">The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well. </p>
|
||||
</a>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[tutorial] A gentle introduction to the gitea doctor</h2>
|
||||
|
|
|
|||
|
|
@ -4,8 +4,44 @@
|
|||
<link href="https://hostea.org/tags/tutorial/atom.xml" rel="self" type="application/atom+xml"/>
|
||||
<link href="https://hostea.org"/>
|
||||
<generator uri="https://www.getzola.org/">Zola</generator>
|
||||
<updated>2022-06-14T00:00:00+00:00</updated>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<id>https://hostea.org/tags/tutorial/atom.xml</id>
|
||||
<entry xml:lang="en">
|
||||
<title>1.17 breaking changes episode 1: preserving a custom gitconfig</title>
|
||||
<published>2022-06-22T00:00:00+00:00</published>
|
||||
<updated>2022-06-22T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/1-17-breaking-episode-1/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/1-17-breaking-episode-1/</id>
|
||||
<content type="html"><p>Before version 1.17, when Gitea needed to change the <a href="https://git-scm.com/docs/git-config">git configuration</a>, it modified the <code>$HOME/.gitconfig</code> file. For instance it would <a href="https://github.com/go-gitea/gitea/blob/release/v1.16/modules/git/git.go#L174-L177">set core.quotePath to false</a>:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[core]
|
||||
</span><span> </span><span style="color:#bf616a;">quotePath </span><span>= </span><span style="color:#d08770;">false
|
||||
</span></code></pre>
|
||||
<p>When installing Gitea <a href="https://docs.gitea.io/en-us/install-with-docker/">from docker</a> or <a href="https://docs.gitea.io/en-us/install-with-docker-rootless/">rootless</a> or even <a href="https://docs.gitea.io/en-us/install-from-binary/">from binary</a> this <code>$HOME/.gitconfig</code> file belongs to a user that is <a href="https://docs.gitea.io/en-us/install-from-binary/#prepare-environment">dedicated to Gitea</a> and not used by anyone else.</p>
|
||||
<p>However, if an Gitea installation was done differently and <code>$HOME/.gitconfig</code> has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:</p>
|
||||
<pre data-lang="ini" style="background-color:#2b303b;color:#c0c5ce;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#b48ead;">[user]
|
||||
</span><span> </span><span style="color:#bf616a;">name </span><span>= Jane Doe
|
||||
</span><span> </span><span style="color:#bf616a;">email </span><span>= jane</span><span style="color:#b48ead;">@doe</span><span>.com
|
||||
</span></code></pre>
|
||||
<p>It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a <strong>potential for breakage when upgrading to Gitea &gt;= 1.17 because the location of the file changed</strong>. It must be moved manually to the new location 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>Repository Root Path</strong> (which is <code>/data/git/repositories</code> in the example above).</li>
|
||||
</ul>
|
||||
<p>The reason why this breaking change was introduced is to workaround <a href="https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
|
||||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>[tutorial] A gentle introduction to the gitea doctor</title>
|
||||
<published>2022-06-14T00:00:00+00:00</published>
|
||||
|
|
|
|||
|
|
@ -209,6 +209,34 @@
|
|||
</a></div>
|
||||
<ul class="blog__list">
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/1-17-breaking-episode-1/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">1.17 breaking changes episode 1: preserving a custom gitconfig</h2>
|
||||
<p class="blog__post-meta">
|
||||
22
|
||||
June
|
||||
|
||||
,
|
||||
2022 · <b>2 min read</b>
|
||||
</p>
|
||||
|
||||
<p class="blog__post-description">The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well. </p>
|
||||
</a>
|
||||
<div class="blog__post-tag-container">
|
||||
|
||||
<a class="blog__post-tag" href="/tags/hostea">#hostea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/gitea">#gitea</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/troubleshoot">#troubleshoot</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/problem">#problem</a>
|
||||
|
||||
<a class="blog__post-tag" href="/tags/tutorial">#tutorial</a>
|
||||
|
||||
</div>
|
||||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/gentle-introduction-to-the-doctor/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[tutorial] A gentle introduction to the gitea doctor</h2>
|
||||
|
|
|
|||
Loading…
Reference in New Issue