From 0ef0f6a90aacd43cec10ecb4c0466e2fcdbb0940 Mon Sep 17 00:00:00 2001
From: arabcoders <admin@arabcoders.org>
Date: Thu, 2 Oct 2025 18:57:05 +0300
Subject: [PATCH] Add Gitea support instructions to FAQ.

---
 .vscode/settings.json |  1 +
 FAQ.md                | 12 ++++++++++++
 2 files changed, 13 insertions(+)

diff --git a/.vscode/settings.json b/.vscode/settings.json
index 8b85e87e..77526555 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -77,6 +77,7 @@
     "Funsafe",
     "getpid",
     "gibibytes",
+    "gitea",
     "gitpython",
     "gpac",
     "hiddenimports",
diff --git a/FAQ.md b/FAQ.md
index 4cd4803a..f0e70d87 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -491,3 +491,15 @@ By default, YTPTube prevents requests to internal resources, for security reason
 
 We do not recommend enabling this option unless you know what you are doing, as it can expose your internal network to 
 potential security risks. This should only be used if it's truly needed.
+
+# How to setup CI on Gitea?
+
+The docker container builder already support self-hosted repositories like Gitea, you simply need to define two things at your repository settings.
+
+1. Create a secret named `GIT_TOKEN` and set it to your Gitea personal access token.
+2. Create a variable named `REGISTRY` and set it to your docker registry, for example `gitea.domain.org`.
+
+Thats it, the `main.yml` will now disable the docker/github container registries, and use your Gitea repository instead. It will follow the usual
+naming, your container name will be named `REGISTRY/ytptube` and the tags will be the same as the ones used in the github registry.
+
+Unfortunately, the `native-builder.yml` workflow doesn't support self-hosted repositories at the moment.