Mirror/gitea-mirror
1
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2025-12-06 11:36:44 +03:00
Code Issues Packages Projects Releases Wiki Activity

updated article

Browse Source
This commit is contained in:
Arunavo Ray
2025-10-22 23:53:30 +05:30
parent 3c808eb0c0
commit fa5f7da5c4
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
www/src/pages/use-cases/backup-github-repositories.mdx
View File

@@ -14,7 +14,7 @@ GitHub is great—right up until an outage, SSO change, or account lockout stran
## Requirements
- Docker Engine and Compose on the host that will run the mirror
- A GitHub personal access token with `repo`, `read:org`, and `admin:org` if you mirror orgs
- A GitHub personal access token (classic) with `repo`, plus the `read:org` checkbox under `admin:org` when you mirror organizations (leave the write/admin boxes unchecked)
- A self-hosted Gitea instance (can be on the same box) and admin or org owner credentials
- Open ports 4321 (web UI) and 3000 (default Gitea) inside your network
@@ -41,7 +41,7 @@ Wait for "Server started" before moving on.
### 2. Generate tokens and connect GitHub
1. Create a GitHub personal access token (classic) with at least `repo`, `read:org`, and `admin:org` if you want organization mirrors.
1. Create a GitHub personal access token (classic) with `repo` enabled and, inside the `admin:org` section, check `read:org` so the mirror can list organization repositories—leave `write:org` and `admin:org` unchecked.
2. Log in to Gitea and create an access token for an admin/owner account with `write:repository`.
3. Visit `http://<host>:4321` and sign up—the first user becomes admin.
4. Complete the setup wizard:

2
www/src/pages/use-cases/preserve-github-history.mdx
View File

@@ -14,7 +14,7 @@ GitHub accounts get banned, repos go private, and owners rage-delete history. If
## Requirements
- Running Gitea Mirror (follow the [backup playbook](../backup-github-repositories/))
- GitHub PAT with metadata scopes (`repo`, `read:org`)
- GitHub PAT with `repo` enabled (add the `read:org` checkbox under `admin:org` when you archive organization repositories; leave write/admin unchecked)
- Destination Gitea with enough disk for cloned repos + attachments
- Optional: object storage or snapshots for long-term archiving of the mirror volume

2
www/src/pages/use-cases/sync-github-to-self-hosted-gitea.mdx
View File

@@ -14,7 +14,7 @@ You may still collaborate on GitHub every day, yet want a LAN Gitea copy you con
## Requirements
- Gitea Mirror deployed (Docker, Proxmox LXC, or Helm)
- GitHub PAT with `repo`, `read:org`, and `admin:org` scopes
- GitHub PAT with `repo` enabled (add the `read:org` checkbox under `admin:org` to mirror organizations; leave write/admin unchecked)
- Gitea API token for the target account/org
- Stable connectivity between the mirror host and both GitHub + Gitea