Skip to content

Different problem with mirroring / sync #8084

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

Closed
jayjupdhig opened this issue Sep 4, 2019 · 16 comments
Closed

Different problem with mirroring / sync #8084

jayjupdhig opened this issue Sep 4, 2019 · 16 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@jayjupdhig
Copy link

There are many problems with mirroring/sync as described here (last entries): https://discourse.gitea.io/t/external-git-server/1425/13

  • When i click "Synchronized", the commits from the mirror server will not be updated in the Web GUI. But they will be updated in the SourceTree GIT client connected to Gitea

  • When i try to commit/push from the SourceTree client (connected with Gitea, not the mirror repo), i got a message with "read only" / 403.

-> The remote/mirroring repo has absolutely no problems with authentication - it never had. It uses basic authentication (Standard authentication by IIS - NOT "Windows Authentication") With SourceTree, it alway worked. -> So no reason for "read only"... The remote repo was never "read only". We need http basic auth for all, read, write, update, delete, whatever...

Regards, Jan

@jayjupdhig jayjupdhig changed the title Different problem with mirrorign / sync Different problem with mirroring / sync Sep 4, 2019
@jayjupdhig
Copy link
Author

And "private" seems to have nothing to do with the "read-only" / 403 problem.

Is "private" the option that prevents the read-only-access for everyone. (Similar to GitHub i think?)

Regards, Jan

@jayjupdhig
Copy link
Author

After a few day i saw the problem (which is not really) with the "Synchronize" button for remote repo in Gitea:

https://discourse.gitea.io/t/external-git-server/1425/13

**_"On the repo main page, there is only 1 entry in vertical direction - even if there are more than 1 commit. So i saw, you have to click on “x Commits” to view all of them…

But the “remote repository is read-only” problem still persists - and no, the remote repo is NOT read-only… how i should done the first (initial) commit when it’s read only…?

And i’m still able to commit on the remote repo when i’m directly connected to it. But not if Gitea is connected to it.

And the http basic auth url stored in gitea works when i copy/paste it to browser bar:

http://admin:[email protected]/WHATEVER

And SourceTree, where i can commit to the repo (directly, no over Gitea) also uses that http basic auth.

So problem 1 i not really a problem, but problem 2 is still unsolved!

How to solve it?

Thank you for your feedbacks,
Jan"_**

....ok, so the "remote repo is readonly" is sill present. I can't say it is a bug, but so it seems it is.

Maybe somebody can proof the opposite - that it's not a bug? If yes, i think we can close that issue.

Regards,
Jan

@jayjupdhig
Copy link
Author

How to make font bold and/or italic here?

There are "markers" like '_**', but they don't change the text format and will be show as plain text

@jayjupdhig
Copy link
Author

maybe the workaround it to commit/push only and directly to the remote repo. never push/commit to gitea.

but it's really really sub-optimal and nothing else..

@jayjupdhig
Copy link
Author

No anwser??

@lunny
Copy link
Member

lunny commented Sep 11, 2019

Which one is your current problem?

@jayjupdhig
Copy link
Author

“remote repository is read-only”

But it's NOT read-only... when i connect with SourceTree, it isn't.

@lafriks
Copy link
Member

lafriks commented Sep 11, 2019

It is not really understandable from Your description where error is shown in Gitea or in SourceTree?

@lafriks lafriks added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Sep 11, 2019
@jayjupdhig
Copy link
Author

  1. create a repo on non git server A
  2. do an initial commit
  3. do a new migration on git server B, that server is with github
  4. create a new migration with "mirror" option to the repo on git server A
  5. set up the git repo from server B, the one with gitea
  6. trying to commit & pull to the git repo on server B (gitea) will fail on that read-only problem

If there are any questions, don't hesitate to ask me.

@jayjupdhig
Copy link
Author

"It is not really understandable from Your description where error is shown in Gitea or in SourceTree?"

Gitea...

@6543
Copy link
Member

6543 commented Oct 3, 2019

giteas repo type "mirror" only mirrors a contend !
if you like to work with it you can converte it to a normal repository - but then it wont mirror a other repository

gitea akts like a real mirror - you CAN change things in the real world but the mirror only display a inverted version wich CANT BE MODIFIED

@6543
Copy link
Member

6543 commented Oct 3, 2019

you perhaps try to setup something like a gitlab mirror where you can also work on the mirror repo - but the technik behind isn't implemented in gitea jet (this can make sync conflict)

@6543
Copy link
Member

6543 commented Oct 3, 2019

@jayjupdhig
Copy link
Author

OK, thx.

What is "contend" ?

"gitea akts like a real mirror - you CAN change things in the real world but the mirror only display a inverted version wich CANT BE MODIFIED"

...all ok, thx again! :-)

@6543
Copy link
Member

6543 commented Oct 9, 2019

What is "contend" ?

commits & branches

@jayjupdhig
Copy link
Author

ok thx

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

4 participants