The Wayback Machine - https://web.archive.org/web/20200928143805/https://github.com/go-gitea/gitea/issues/12018
Skip to content

/ gitea

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migration does not clone repository from the proxy #12018

Open
Zoranner opened this issue Jun 22, 2020 · 6 comments
Open

Migration does not clone repository from the proxy #12018

Zoranner opened this issue Jun 22, 2020 · 6 comments
Labels
good first issue kind/feature reviewed/confirmed

Comments

@Zoranner
Copy link

@Zoranner Zoranner commented Jun 22, 2020 •
edited

  • Gitea version (or commit ref): 1.12.1
  • Git version: 2.27.0
  • Operating system: Windows 10
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    Nothing.

Description

I configured git's global http & https proxy to http://127.0.0.1:1086, but it seems that migration does not clone repository from the proxy.

Screenshots

Nothing.
@lunny lunny added the kind/feature label Jun 23, 2020
@lunny
Copy link
Member

@lunny lunny commented Jun 23, 2020

We need a global proxy setting for all the external http request not only webhook.
@Zoranner
Copy link
Author

@Zoranner Zoranner commented Jun 25, 2020

@lunny 麻烦问一下，现阶段有没有什么临时的解决方案可以解决Gitea迁移仓库不走全局代理设置的问题，大部分时候在国内Clone Github的项目都会特别慢，没有代理迁移项目太难了😣
@lunny
Copy link
Member

@lunny lunny commented Jun 26, 2020

I think we need a global proxy setting.
@stale
Copy link

@stale stale bot commented Aug 30, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
@stale stale bot added the stale label Aug 30, 2020
@stale
Copy link

@stale stale bot commented Sep 13, 2020

This issue has been automatically closed because of inactivity. You can re-open it if needed.
@stale stale bot closed this Sep 13, 2020
@zeripath zeripath reopened this Sep 13, 2020
@stale stale bot removed the stale label Sep 13, 2020
@zeripath
Copy link
Contributor

@zeripath zeripath commented Sep 13, 2020

This would likely be a good first issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue kind/feature reviewed/confirmed
3 participants
@lunny @zeripath @Zoranner
You can’t perform that action at this time.