Changes for page How to set up a gitea docker instance
Last modified by Alexandru Pentilescu on 2024/07/16 22:44
From version 12.1
edited by Alexandru Pentilescu
on 2024/07/16 21:54
on 2024/07/16 21:54
Change comment:
Upload new image "1.png", version 1.1
To version 8.1
edited by Alexandru Pentilescu
on 2024/07/16 21:35
on 2024/07/16 21:35
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -154,7 +154,6 @@ 154 154 If you need more configuration information, check [[this>>https://docs.gitea.com/administration/config-cheat-sheet]] out. 155 155 156 156 = Activating SSH passthrough = 157 - 158 158 This is the most complex step out of all of them. In order to take advantage of the fact that SSH git pulls/pushes will be done via standard port 22, normal SSH traffic needs to be differentiated from git specific SSH traffic. 159 159 160 160 To this end, multiple configurations will need to be done. ... ... @@ -168,7 +168,6 @@ 168 168 While this isn't the end of the world, ideally, all SSH traffic should be routed to port 22, as is standard. VPS firewalls or intermediary ISPs may, themselves, block off incoming or outgoing traffic to unconventional ports, which can cause issues. As such, using the standard port 22 for SSH communication would be ideal. 169 169 170 170 == Enable SSH login for the git user == 171 - 172 172 So, to enable SSH capabilities to the git user, please edit the "/etc/ssh/sshd_config" configuration and change the following line: 173 173 174 174 {{code language="text"}} ... ... @@ -180,11 +180,3 @@ 180 180 {{code language="bash"}} 181 181 systemctl restart ssh 182 182 {{/code}} 183 - 184 -== Generate a proper public/private keypair for all the accounts that need to use git via SSH with == 185 - 186 -This part's pretty self explanatory. 187 - 188 -For each user, on each device, that will require SSH git access to the aforementioned git server, they will need to have their own public/private authentication keypair set under a Gitea user that's already registered on the Gitea web portal. 189 - 190 -
- 1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.AlexandruPentilescu - Size
-
... ... @@ -1,1 +1,0 @@ 1 -285.4 KB - Content
- 2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.AlexandruPentilescu - Size
-
... ... @@ -1,1 +1,0 @@ 1 -589.7 KB - Content
- 3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.AlexandruPentilescu - Size
-
... ... @@ -1,1 +1,0 @@ 1 -635.2 KB - Content