From 3728b07d20e9abbf74bc3bdf9562f3327f8a5c3e Mon Sep 17 00:00:00 2001
From: jochens <jschoubben@gmail.com>
Date: Wed, 30 Sep 2026 12:36:24 +0200
Subject: [PATCH] Leave gitea's 222:22 to its own decision

A controller test holds git-over-ssh at 222 as the mesh's fixed convention
when no node says otherwise (TestTheForgesSshPortIsTheMeshsFixedConvention
ByDefault): without a setting, the short form would publish 22:22 and
collide with the machine's own sshd. Changing that is a decision, not part
of this sweep.
---
 modules/gitea/module.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/gitea/module.json b/modules/gitea/module.json
index 24f231b..c7f1ac4 100644
--- a/modules/gitea/module.json
+++ b/modules/gitea/module.json
@@ -55,7 +55,7 @@
       "port": 22,
       "protocol": "tcp",
       "from": "mesh",
-      "why": "git over ssh, gitea's own unmodified sshd. Its machine port is the assignment's: never 22, which the machine's own daemon holds and a module does not take"
+      "why": "git over ssh, gitea's own unmodified sshd. Published on the machine's own side at 222, the mesh's fixed public convention \u2014 not 22, which the machine's own daemon holds and a module does not take"
     }
   ],
   "serves": {
@@ -140,7 +140,7 @@
       ],
       "ports": [
         "3000",
-        "22"
+        "222:22"
       ],
       "volumes": [
         "${dir:data}:/data"