Mirror/gitea-mirror
1
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-03-13 22:12:54 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #181 from RayLabsHQ/codex/issue-171-sync-reporting

Browse Source 
Clarify mirror sync status and token-rotation troubleshooting
This commit is contained in:
ARUNAVO RAY
2026-02-24 10:12:40 +05:30
committed by GitHub
parent 25854b04f9 888089b2d5
commit b1ca8c46bf
2 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -301,6 +301,14 @@ CLEANUP_DRY_RUN=false # Set to true to test without changes
If using a reverse proxy (e.g., nginx proxy manager) and experiencing issues with JavaScript files not loading properly, try enabling HTTP/2 support in your proxy configuration. While not required by the application, some proxy configurations may have better compatibility with HTTP/2 enabled. See [issue #43](https://github.com/RayLabsHQ/gitea-mirror/issues/43) for reference. If using a reverse proxy (e.g., nginx proxy manager) and experiencing issues with JavaScript files not loading properly, try enabling HTTP/2 support in your proxy configuration. While not required by the application, some proxy configurations may have better compatibility with HTTP/2 enabled. See [issue #43](https://github.com/RayLabsHQ/gitea-mirror/issues/43) for reference.
### Mirror Token Rotation (GitHub Token Changed)
For existing pull-mirror repositories, changing the GitHub token in Gitea Mirror does not always update stored mirror credentials in Gitea/Forgejo for already-created repositories.
If sync logs show authentication failures (for example `terminal prompts disabled`), do one of the following:
1. In Gitea/Forgejo, open repository **Settings → Mirror Settings** and update the mirror authorization password/token.
2. Or delete and re-mirror the repository from Gitea Mirror so it is recreated with current credentials.
### Re-sync Metadata After Changing Mirror Options ### Re-sync Metadata After Changing Mirror Options
If you enable metadata options (issues/PRs/labels/milestones/releases) after repositories were already mirrored: If you enable metadata options (issues/PRs/labels/milestones/releases) after repositories were already mirrored:

6
src/lib/gitea-enhanced.ts
View File

@@ -587,12 +587,12 @@ export async function syncGiteaRepoEnhanced({
userId: config.userId, userId: config.userId,
repositoryId: repository.id, repositoryId: repository.id,
repositoryName: repository.name, repositoryName: repository.name,
message: `Successfully synced repository: ${repository.name}`, message: `Sync requested for repository: ${repository.name}`,
details: `Repository ${repository.name} was synced with Gitea.`, details: `Mirror sync was requested for ${repository.name}. Gitea/Forgejo performs the actual pull asynchronously; check remote logs for pull errors.`,
status: "synced", status: "synced",
}); });
console.log(`[Sync] Repository ${repository.name} synced successfully`); console.log(`[Sync] Mirror sync requested for repository ${repository.name}`);
return response.data; return response.data;
} catch (syncError) { } catch (syncError) {
if (syncError instanceof HttpError && syncError.status === 400) { if (syncError instanceof HttpError && syncError.status === 400) {