diff --git a/about/index.html b/about/index.html index e1ca2d8..371b06d 100644 --- a/about/index.html +++ b/about/index.html @@ -8,11 +8,11 @@ - + @@ -24,11 +24,11 @@ - + @@ -43,7 +43,7 @@ - + @@ -145,7 +145,7 @@
- Hostea temporary logo

ostea @@ -179,7 +179,7 @@

- Forum + Forum
@@ -220,7 +220,7 @@

You can rely on Gna! if you are an individual software developer who need their own Gitea instance with CI but can't be bothered with installation and maintenance. You want the freedom to download a backup and seamlessly self-host it whenever you decide: no strings attached.

If you are into trouble and need assistance with a Gitea instance not hosted at Gna!, you can ask for help at the Gna! clinic. The doctors have developped a unique expertise and are well equiped to help you recover and upgrade.

-

Do you already have an expertise running Gitea? You are welcome to join the Gna! collective, get in touch in the forum or the chat.

+

Do you already have an expertise running Gitea? You are welcome to join the Gna! collective, get in touch in the forum or the chat.

@@ -259,7 +259,7 @@
Email icon @@ -273,7 +273,7 @@ Privacy | - + @@ -24,11 +24,11 @@ - + @@ -43,7 +43,7 @@ - + @@ -145,7 +145,7 @@
- Hostea temporary logo

ostea @@ -179,7 +179,7 @@

- Forum + Forum
@@ -242,7 +242,7 @@

It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a potential for breakage when upgrading to Gitea >= 1.17 because the location of the file changed. It must be moved manually to the new location as follows:

$ gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor 
 [1] Check paths and basic configuration
@@ -257,7 +257,7 @@
 
    
 
  • Copy the $HOME/.gitconfig file to the Repository Root Path (which is /data/git/repositories in the example above).
    • 
 

-
The reason why this breaking change was introduced is to workaround a rare problem impacting Gitea installations relying on networked volumes.

+
The reason why this breaking change was introduced is to workaround a rare problem impacting Gitea installations relying on networked volumes.

@@ -312,7 +312,7 @@
Email icon @@ -326,7 +326,7 @@ Privacy | - + @@ -24,11 +24,11 @@ - + @@ -43,7 +43,7 @@ - + @@ -145,7 +145,7 @@
- Hostea temporary logo

ostea @@ -179,7 +179,7 @@

- Forum + Forum
@@ -235,7 +235,7 @@

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
@@ -304,7 +304,7 @@
     

       
         Email icon
@@ -318,7 +318,7 @@
       Privacy
       |
       
     
     
-    
+    
     
 
 	
@@ -24,11 +24,11 @@
 
 
    
-    
+    
     
 
     
@@ -43,7 +43,7 @@
 
     
     
-    
+    
 
     
     
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
 
@@ -145,7 +145,7 @@
   

     
 
-      Hostea temporary logo
       

       ostea
@@ -179,7 +179,7 @@
 
     
   

-    Forum
+    Forum
   

 
     
@@ -230,7 +230,7 @@
 
 
   

-    
Introducing Hostea, a project Loïc
+    
Introducing Hostea, a project Loïc
 Dachary and Aravinth
 Manivannan are working on to create a full Free
 software development suite based on
@@ -308,7 +308,7 @@ to learn more about the event.

     

       
         Email icon
@@ -322,7 +322,7 @@ to learn more about the event.

       Privacy
       |
       
 
 	 - Posts
-	
-  
+	
+  
 	Zola
 	2022-07-20T00:00:00+00:00
-	https://hostea.org/blog/atom.xml
+	https://gna.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/
+		
+		https://gna.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>
+<li>Figure out the directory where <code>$HOME/.gitconfig</code> must be moved by <a href="https://gna.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
@@ -38,14 +38,14 @@
 		Get a Gitea instance with CI at Hostea
 		2022-07-10T00:00:00+00:00
 		2022-07-10T00:00:00+00:00
-		
-		https://hostea.org/blog/experimental/
+		
+		https://gna.org/blog/experimental/
 		<p>Hosting a Gitea instance on Hostea is now possible (but still experimental). It is meant to be a minimum viable product: anyone can <a href="https://hosteadashboard.gna.org">create a new dedicated Gitea instance</a> within minutes and pay for it on a monthly basis with a credit card. It includes a dedicated CI based on <a href="https://woodpecker-ci.org/">Woodpecker</a>. The smallest instance costs 10€ per month (2GB RAM, 10GB disk, 1CPU) and will be a good fit for a freelance up to a team of five people but bigger instances are also available if more RAM, CPU or disk is required.</p>
 <video width="600" controls>
   <source src="https://cloud.forgefriends.org/s/xXLcYpsE469tJEj/download?path=&files=hostea-screencast-vm-create.mp4" type="video/mp4" />
 </video>
 <p>The service is 100% infrastructure as code, published as <a href="https://lab.enough.community/main/infrastructure/-/tree/9e18ebbf675c8a65d1585d20b4cf6295af6e52ed/playbooks/hosteadashboard">Ansible playbooks within Enough</a>. It can be self-hosted on bare metal (with <a href="https://libvirt.org/">libvirt</a>) or in the cloud (with <a href="https://www.openstack.org/">OpenStack</a>): follow the <a href="https://enough-community.readthedocs.io/en/latest/introduction.html#quick-start">quick start</a>, configure playbooks for <a href="https://enough-community.readthedocs.io/en/latest/services/hostea.html">hostea</a> and <a href="https://enough-community.readthedocs.io/en/latest/services/hosteadashboard.html">the dashboard</a>.</p>
-<p>The organization supporting Hostea is a <a href="https://forum.hostea.org/c/governance-and-decisions/7">horizontal collective</a> of individuals and organizations. The <a href="https://forum.hostea.org/t/decision-revenue-sharing-model/92">revenue sharing model</a> is set to dedicate 25% of the income (more than the profits) to help the Free Software projects Hostea depends on such as Gitea, Enough, Django etc.</p>
+<p>The organization supporting Hostea is a <a href="https://forum.gna.org/c/governance-and-decisions/7">horizontal collective</a> of individuals and organizations. The <a href="https://forum.hostea.org/t/decision-revenue-sharing-model/92">revenue sharing model</a> is set to dedicate 25% of the income (more than the profits) to help the Free Software projects Hostea depends on such as Gitea, Enough, Django etc.</p>
 <h3 id="the-origin">The origin<a class="zola-anchor" href="#the-origin" aria-label="Anchor link for: the-origin"
   ><span class="anchor-icon">#</span></a
 >
@@ -58,13 +58,13 @@
 </h3>
 <p>The most common mistake technical people do when creating a new piece of software is to overlook the fact that they have absolutely no idea how to let their intended user base know about it. Maybe the reason it happens so often is because it is very difficult to resist the urge of creating something. Because that's what technical people love to do: create things, even when they have no clue if it can be used.</p>
 <p>It took no longer than two weeks for the people involved in Hostea to decide to build the technical stack to run hostea instead of being reasonable and give up. It was just too tempting.</p>
-<p>To keep the madness contained and enjoyable, it was decided to set a deadline to July 1st and to <a href="https://gitea.hostea.org/Hostea/july-mvp/issues">define precise and realistic technical goals</a>. It turned out to be an enjoyable experience: everyone learned a lot in the process and the outcome is something that can be reproduced. Most MVPs are a brittle pile of hacks designed to last a few weeks and be thrown away. But since a primary goal of the project was to create something self-hostable, it had to implement that feature and therefore be reproducible.</p>
+<p>To keep the madness contained and enjoyable, it was decided to set a deadline to July 1st and to <a href="https://gitea.gna.org/Hostea/july-mvp/issues">define precise and realistic technical goals</a>. It turned out to be an enjoyable experience: everyone learned a lot in the process and the outcome is something that can be reproduced. Most MVPs are a brittle pile of hacks designed to last a few weeks and be thrown away. But since a primary goal of the project was to create something self-hostable, it had to implement that feature and therefore be reproducible.</p>
 <h3 id="a-horizontal-collective-with-a-revenue-sharing-model">A horizontal collective with a revenue sharing model<a class="zola-anchor" href="#a-horizontal-collective-with-a-revenue-sharing-model" aria-label="Anchor link for: a-horizontal-collective-with-a-revenue-sharing-model"
   ><span class="anchor-icon">#</span></a
 >
 </h3>
-<p>Another goal of Hostea is to deploy federated forges, even at an experimental stage. Instead of creating a centralized organization to support Hostea, it was decided to create <a href="https://forum.hostea.org/c/governance-and-decisions/7">horizontal collective</a>. It feels like a contradiction for a project committed to decentralization to be governed by a centralized organization.</p>
-<p>The collective is composed of individuals and organizations but, unlike exclusively volunteer based Free Software projects, it is for profit. Customers rent Gitea instances by the month and the income is used to pay for expenses. There is however a difficulty: by nature a horizontal collective cannot be incorporated as it would create a level of hierarchy. The <a href="https://forum.hostea.org/t/decision-revenue-sharing-model/92">revenue sharing model</a> had to be set as an informal agreement between members where one of them receives the income and distributes it to the others, depending on their Hostea related expenses.</p>
+<p>Another goal of Hostea is to deploy federated forges, even at an experimental stage. Instead of creating a centralized organization to support Hostea, it was decided to create <a href="https://forum.gna.org/c/governance-and-decisions/7">horizontal collective</a>. It feels like a contradiction for a project committed to decentralization to be governed by a centralized organization.</p>
+<p>The collective is composed of individuals and organizations but, unlike exclusively volunteer based Free Software projects, it is for profit. Customers rent Gitea instances by the month and the income is used to pay for expenses. There is however a difficulty: by nature a horizontal collective cannot be incorporated as it would create a level of hierarchy. The <a href="https://forum.gna.org/t/decision-revenue-sharing-model/92">revenue sharing model</a> had to be set as an informal agreement between members where one of them receives the income and distributes it to the others, depending on their Hostea related expenses.</p>
 <p>It also requires that 25% of the income (not the profits) is dedicated to help the Free Software projects that Hostea depends on such as Gitea, Enough, Django etc. It can be via a donation, by upstreaming a bug fix or any kind of work that is beneficial to the dependency.</p>
 <h3 id="dedicated-to-forge-federation">Dedicated to forge federation<a class="zola-anchor" href="#dedicated-to-forge-federation" aria-label="Anchor link for: dedicated-to-forge-federation"
   ><span class="anchor-icon">#</span></a
@@ -77,8 +77,8 @@
 		1.17 breaking changes episode 1: preserving a custom gitconfig
 		2022-06-22T00:00:00+00:00
 		2022-06-22T00:00:00+00:00
-		
-		https://hostea.org/blog/1-17-breaking-episode-1/
+		
+		https://gna.org/blog/1-17-breaking-episode-1/
 		<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
@@ -91,7 +91,7 @@
 </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>
+<li>Figure out the directory where <code>$HOME/.gitconfig</code> must be moved by <a href="https://gna.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
@@ -106,16 +106,16 @@
 <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>
+<p>The reason why this breaking change was introduced is to workaround <a href="https://gna.org/blog/unsafe-repository-is-owned-by-someone-else/">a rare problem</a> impacting Gitea installations relying on networked volumes.</p>
 
 	
 	
 		[tutorial] A gentle introduction to the gitea doctor
 		2022-06-14T00:00:00+00:00
 		2022-06-14T00:00:00+00:00
-		
-		https://hostea.org/blog/gentle-introduction-to-the-doctor/
-		<p>While helping people with their upgrades <a href="https://discourse.gitea.io/t/migration-from-1-2-to-1-16-8/5309">in the Gitea forum</a> or <a href="https://forum.hostea.org/t/gitea-upgrade-from-1-14-1-to-1-16-8/90">at the Hostea clinic</a>, I realized that few Gitea admins know about the <a href="https://docs.gitea.io/en-us/command-line/#doctor"><code>gitea doctor</code></a> command and decided to write this blog post as a gentle introduction.</p>
+		
+		https://gna.org/blog/gentle-introduction-to-the-doctor/
+		<p>While helping people with their upgrades <a href="https://discourse.gitea.io/t/migration-from-1-2-to-1-16-8/5309">in the Gitea forum</a> or <a href="https://forum.gna.org/t/gitea-upgrade-from-1-14-1-to-1-16-8/90">at the Hostea clinic</a>, I realized that few Gitea admins know about the <a href="https://docs.gitea.io/en-us/command-line/#doctor"><code>gitea doctor</code></a> command and decided to write this blog post as a gentle introduction.</p>
 <h3 id="an-apple-a-day-keeps-the-doctor-away">An apple a day keeps the doctor away<a class="zola-anchor" href="#an-apple-a-day-keeps-the-doctor-away" aria-label="Anchor link for: an-apple-a-day-keeps-the-doctor-away"
   ><span class="anchor-icon">#</span></a
 >
@@ -239,8 +239,8 @@
 		[solved] Zombies created by Gitea
 		2022-06-04T00:00:00+00:00
 		2022-06-04T00:00:00+00:00
-		
-		https://hostea.org/blog/zombies-part-2/
+		
+		https://gna.org/blog/zombies-part-2/
 		<p>Gitea can <a href="/blog/zombies">create zombies</a>, for instance if a Git mirror takes too long. When updating a mirror, Gitea relies on the <code>git remote update</code> command which creates a child process, <code>git-remote-https</code>, to fetch data from the remote repository. Gitea has an internal timeout that will kill the child process (e.g. <code>git remote update</code>) when it takes too long but will not kill the grandchild. This grandchild will become an orphan and run forever or until its own timeout expires, which is about two minutes on git version 2.25.</p>
 <pre style="background-color:#2b303b;color:#c0c5ce;"><code><span>$ time git clone https://4.4.4.4
 </span><span>Clonage dans &#39;4.4.4.4&#39;...
@@ -301,8 +301,8 @@
 		[diagnostic] Zombies created by Gitea
 		2022-06-02T00:00:00+00:00
 		2022-06-02T00:00:00+00:00
-		
-		https://hostea.org/blog/zombies/
+		
+		https://gna.org/blog/zombies/
 		<p>The first <a href="https://github.com/go-gitea/gitea/issues/3242">issue about zombie processes</a> created by Gitea was reported in 2017 and <a href="https://github.com/go-gitea/gitea/issues/13987">resurfaced</a> on a <a href="https://github.com/go-gitea/gitea/issues/19077">regular basis</a>. Although it does not look pretty, zombie processes are leftovers that do not consume resources and never caused any kind of harm. Here is one scenario that will create a zombie:</p>
 <ul>
 <li>Gitea updates a mirror by spawning the process <code>git remote update</code></li>
@@ -369,8 +369,8 @@
 		[solved] Gitea 1.15 and up: path not found or permission denied
 		2022-05-28T00:00:00+00:00
 		2022-05-28T00:00:00+00:00
-		
-		https://hostea.org/blog/path-not-found/
+		
+		https://gna.org/blog/path-not-found/
 		<p>In Gitea 1.15 the <a href="https://github.com/go-gitea/gitea/blob/cfb4c23a5009b9c236d48ac0bc156577c7d70741/custom/conf/app.example.ini">app.example.ini</a> file was changed to <a href="https://github.com/go-gitea/gitea/commit/4a84022d2559ccfc99960c7c654ee8b9b38664f7">comment out most of the values</a>. The assumption was that all values exactly matched the defaults <a href="https://github.com/go-gitea/gitea/blob/main/modules/setting/setting.go">in the source code</a>. However, there are differences, for instance for <a href="https://github.com/go-gitea/gitea/blob/cfb4c23a5009b9c236d48ac0bc156577c7d70741/modules/setting/setting.go#L771">APP_DATA_PATH</a>. Before Gitea 1.15, <code>app.example.ini</code> contained:</p>
 <pre style="background-color:#2b303b;color:#c0c5ce;"><code><span>APP_DATA_PATH = data
 </span></code></pre>
@@ -393,8 +393,8 @@
 		[solved] Gitea 1.16.[678] error: fatal: unsafe repository is owned by someone else
 		2022-05-15T00:00:00+00:00
 		2022-05-15T00:00:00+00:00
-		
-		https://hostea.org/blog/unsafe-repository-is-owned-by-someone-else/
+		
+		https://gna.org/blog/unsafe-repository-is-owned-by-someone-else/
 		<p>April 12, 2022 version <a href="https://lore.kernel.org/git/xmqqv8veb5i6.fsf@gitster.g/">git v2.35.2</a> was released  and addresses a security issue <a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a>. It was backported to 2.30.3, v2.31.2, v2.32.1, v2.33.2, and v2.34.2 and published by distributions such as <a href="https://security-tracker.debian.org/tracker/CVE-2022-24765">Debian GNU/Linux</a>, <a href="https://www.alpinelinux.org/releases/">Alpine</a>.</p>
 <p><strong>If Gitea runs as user <code>foo</code>, calls a patched Git version and a parent directory of the git repositories is owned by a user other than <code>foo</code>, it will fail</strong> with a message such as:</p>
 <pre style="background-color:#2b303b;color:#c0c5ce;"><code><span>Failed to open repository: Git/Data Error: exit status 128 - fatal: unsafe repository (&#39;/data/git/repositories/git/data.git&#39; is owned by someone else)
@@ -437,10 +437,10 @@
 		[solved] blank or error 500 page after login
 		2022-05-08T00:00:00+00:00
 		2022-05-08T00:00:00+00:00
-		
-		https://hostea.org/blog/blank-or-error-500-page-after-login/
+		
+		https://gna.org/blog/blank-or-error-500-page-after-login/
 		<p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
-<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
+<p>An <a href="https://forum.gna.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
 <ul>
 <li>Upgrade directly to the latest Gitea version, there is no need to upgrade to intermediate versions.</li>
 <li>If the upgrade from version x.y to version x.y+2 fails and there is a need to narrow down the problem, try upgrading to the latest minor version of each major version and verify it works.</li>
@@ -467,7 +467,7 @@
   ><span class="anchor-icon">#</span></a
 >
 </h1>
-<p>The <a href="https://hostea.org/gitea-clinic/">Hostea Clinic</a> is a collective of individual and companies that provides professional services to Gitea admins. They are active members of the Gitea community who <a href="https://discourse.gitea.io/u/dachary/activity">help out</a> as volunteers. They can also be hired to resolve the more complicated cases.</p>
+<p>The <a href="https://gna.org/gitea-clinic/">Hostea Clinic</a> is a collective of individual and companies that provides professional services to Gitea admins. They are active members of the Gitea community who <a href="https://discourse.gitea.io/u/dachary/activity">help out</a> as volunteers. They can also be hired to resolve the more complicated cases.</p>
 <p>The Gitea instance that was in trouble required more than a few minutes of work and access to the database content for a proper diagnostic. They <a href="https://discourse.gitea.io/t/blank-page-after-login/5051/13">proposed their assistance</a> but although <a href="https://discourse.gitea.io/t/user-research-about-gitea-upgrade-experiences-call-for-volunteers/5063/2">well received</a>, it was not accepted.</p>
 <p>When the Gitea admin explained how they chose to resolve the problem <a href="https://discourse.gitea.io/t/blank-page-after-login/5051/14">on the forum</a>, it confirmed the workaround was viable and the root problem was identified. That was enough to figure out a fix for the underlying bug with <a href="https://discourse.gitea.io/t/blank-page-after-login/5051/17">a rather simple patch</a> that was merged <a href="https://github.com/go-gitea/gitea/pull/19629">and backported</a> in the following days. But it happened too late to avoid the data loss.</p>
 <p>To summarize with a timeline, here is what happened:</p>
@@ -481,7 +481,7 @@
 <p>And in retrospect, here is what could have happened instead:</p>
 <ul>
 <li>J+1: The <strong>problem is discovered</strong> by users who see a blank page after login</li>
-<li>J+1: The Gitea admin <strong><a href="https://hostea.org/gitea-clinic/">reaches out to someone at the Hostea Clinic</a></strong></li>
+<li>J+1: The Gitea admin <strong><a href="https://gna.org/gitea-clinic/">reaches out to someone at the Hostea Clinic</a></strong></li>
 <li>J+2: The <a href="https://discourse.gitea.io/t/blank-page-after-login/5051/12">logs of the Gitea instance</a> are analyzed, <strong>the root cause diagnosed</strong> and <a href="https://discourse.gitea.io/t/blank-page-after-login/5051/17">a patch</a> is created to fix it.</li>
 <li>J+3: If necessary a Gitea binary is created with the patch and used as a temporary replacement until the next point release is published with <a href="https://github.com/go-gitea/gitea/pull/19629">the backport</a>. The Gitea admin runs the patched Gitea binary in the meantime. <strong>There is no data loss</strong>.</li>
 </ul>
@@ -492,9 +492,9 @@
 		Introducing Hostea
 		2022-04-22T00:00:00+00:00
 		2022-04-22T00:00:00+00:00
-		
-		https://hostea.org/blog/22-04-2022-hostea-introducing-hostea-forgefriends-monthly-meet/
-		<p>Introducing <a href="https://hostea.org">Hostea</a>, a project <a href="https://dachary.org">Loïc
+		
+		https://gna.org/blog/22-04-2022-hostea-introducing-hostea-forgefriends-monthly-meet/
+		<p>Introducing <a href="https://gna.org">Hostea</a>, a project <a href="https://dachary.org">Loïc
 Dachary</a> and <a href="https://batsense.net">Aravinth
 Manivannan</a> are working on to create a full Free
 software development suite based on
@@ -530,8 +530,8 @@ to learn more about the event.</p>
 		Project plans for a hosted Gitea online service
 		2022-04-18T00:00:00+00:00
 		2022-04-18T00:00:00+00:00
-		
-		https://hostea.org/blog/project-plans-for-hosted-gitea-online-service/
+		
+		https://gna.org/blog/project-plans-for-hosted-gitea-online-service/
 		<p><em>This post was originally published on <a href="https://blog.dachary.org/2022/02/16/project-plans-for-a-hosted-gitea-online-service/">Loïc Dachary's
 blog</a>.</em></p>
 <hr />
diff --git a/blog/blank-or-error-500-page-after-login/index.html b/blog/blank-or-error-500-page-after-login/index.html
index 606a723..7a04939 100644
--- a/blog/blank-or-error-500-page-after-login/index.html
+++ b/blog/blank-or-error-500-page-after-login/index.html
@@ -8,11 +8,11 @@
     
     
     
-    
+    
     
 
 	
@@ -24,11 +24,11 @@
 
 
    
-    
+    
     
 
     
@@ -43,7 +43,7 @@
 
     
     
-    
+    
 
     
     
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
 
@@ -145,7 +145,7 @@
   

     
 
-      Hostea temporary logo
       

       ostea
@@ -179,7 +179,7 @@
 
     
   

-    Forum
+    Forum
   

 
     
@@ -231,7 +231,7 @@
 
   

     
The instructions to upgrade a Gitea instance only require three to four steps. They work fine most of the time but the documentation is lacking a "Troubleshooting" section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.

-
An inventory of the known upgrade issues was started to figure out how to structure such a section in the documentation. The release notes were analyzed all the way back to Gitea 1.9.6 and the work is still in progress. Here is a sample of the tips that will be included:

+
An inventory of the known upgrade issues was started to figure out how to structure such a section in the documentation. The release notes were analyzed all the way back to Gitea 1.9.6 and the work is still in progress. Here is a sample of the tips that will be included: