From 4ea4252d37946ad0e31abd0761aecf06074e3bee Mon Sep 17 00:00:00 2001
From: whitney <whitney.server@gmail.com>
Date: Tue, 7 Nov 2023 14:04:13 -0800
Subject: [PATCH] update readme

---
 gitea/README.md | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/gitea/README.md b/gitea/README.md
index ae71515..75322e1 100644
--- a/gitea/README.md
+++ b/gitea/README.md
@@ -28,6 +28,12 @@ This goes in the [server] section. (https://docs.gitea.com/next/administration/c
 
 `LOCAL_ROOT_URL = http://localhost:3000/`
 
+Also modify the following:
+
+`ROOT_URL = https://git.whitney.rip`
+
+`SSH_DOMAIN = git.whitney.rip`
+
 Then start containers again.
 
 5. Go to xxx.xxx.xx.xxx:3300 and fill out initial config.
@@ -38,7 +44,16 @@ Some things that were weird:
 
 - had to make sure to specify database container by the right name. Removed custom name and used just "database".
 
-6. Handle Authentication like you'd do on Github with SSH keys etc.
+6. Enable SSH on the server
+
+- install openssh-server
+
+- follow `https://wiki.archlinux.org/title/Gitea#Enable_SSH_Support`
+
+Should be able to clone via HTTPS at this point.
+
+7. Handle user authentication like you'd do on Github by generating new ssh keys and adding them to the SSH Keys section.
 
 Settings > SSH/GPG Keys > Manage SSH Keys
 
+Now should also be able to clone with SSH.