[GH-ISSUE #154] Feature Request: Having an "external" link for the local repository #73

New issue

Closed

opened 2026-02-27 15:54:57 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:54:57 +03:00

Owner

Originally created by @arkangelll13 on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/154

Originally assigned to: @arunavo4 on GitHub.

Currently there is a nice clickable link on the dashboard/repositories pages to easily open the local repo where the mirrored files go, this is using the "Gitea URL" to create the link. Is it possible to have an additional field here for the link generation, that is separate from the actual link used by the application to do the mirroring?

My scenario: I have a dedicated (docker) network for gitea and this is where I also put gitea-mirror. I also have a leg here for my reverse proxy and both containers are only available through that reverse proxy. But gitea-mirror is using the direct link to gitea, it does not goes through the proxy.

This way the gitea URL could be like it is for me right now: http://gitea-server:3000 and there could be an extra (optional!) field where the external link coud be for the gitea server: https://gitea.home.lab

Originally created by @arkangelll13 on GitHub (Nov 14, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/154 Originally assigned to: @arunavo4 on GitHub. Currently there is a nice clickable link on the dashboard/repositories pages to easily open the local repo where the mirrored files go, this is using the "Gitea URL" to create the link. Is it possible to have an additional field here for the link generation, that is separate from the actual link used by the application to do the mirroring? My scenario: I have a dedicated (docker) network for gitea and this is where I also put gitea-mirror. I also have a leg here for my reverse proxy and both containers are only available through that reverse proxy. But gitea-mirror is using the direct link to gitea, it does not goes through the proxy. This way the gitea URL could be like it is for me right now: http://gitea-server:3000 and there could be an extra (optional!) field where the external link coud be for the gitea server: https://gitea.home.lab

kerem closed this issue

2026-02-27 15:54:57 +03:00

kerem commented

2026-02-27 15:54:58 +03:00

Author

Owner

@arunavo4 commented on GitHub (Nov 14, 2025):

@arkangelll13 yea I think this is useful will add this soon. If possible this weekend.

@arunavo4 commented on GitHub (Nov 14, 2025): @arkangelll13 yea I think this is useful will add this soon. If possible this weekend.

kerem commented

2026-02-27 15:54:58 +03:00

Author

Owner

@arunavo4 commented on GitHub (Feb 24, 2026):

Implemented in PR: https://github.com/RayLabsHQ/gitea-mirror/pull/183

What was added:

New optional Gitea External URL field in Configuration.
Dashboard repository/org links now use External URL when set, and fall back to Gitea URL.
Mirroring/API operations still use the regular Gitea URL, so existing sync behavior stays the same.
Added env var support: GITEA_EXTERNAL_URL.

This should match the reverse-proxy/internal-network setup you described.

@arunavo4 commented on GitHub (Feb 24, 2026): Implemented in PR: https://github.com/RayLabsHQ/gitea-mirror/pull/183 What was added: - New optional Gitea External URL field in Configuration. - Dashboard repository/org links now use External URL when set, and fall back to Gitea URL. - Mirroring/API operations still use the regular Gitea URL, so existing sync behavior stays the same. - Added env var support: GITEA_EXTERNAL_URL. This should match the reverse-proxy/internal-network setup you described.

kerem referenced this issue

2026-02-27 15:55:18 +03:00

[PR #124] [MERGED] Fix/sso stability #143