Skip to content
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

Issue after initial sync #14

Open
Aetherinox opened this issue Oct 4, 2023 · 3 comments
Open

Issue after initial sync #14

Aetherinox opened this issue Oct 4, 2023 · 3 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested

Comments

@Aetherinox
Copy link

Aetherinox commented Oct 4, 2023

I tried this out and so far I've loved it. Yesterday it seemed to be doing fine. However today I noticed when I created a new repo, it synced the initial repo but stopped syncing after that point. I have the delay variable set to 1800 seconds,

DELAY=1800

However, after the initial commit, it hasn't pushed anymore updates to the repo from Github to Gitea.

I've attempted to restart the docker container, and even shut it off and re-launch it after verifying the docker-compose.yml was alright.

Any ideas of where to look? Hopefully it's just a small thing, because I love the idea of this app, and it's vital to the setup I have. Am I losing my mind or is it supposed to keep mirroring each time the delay expires? I swear I saw it doing multiple commits.

Edit: Something I noticed. If I go into the repo settings, I noticed that each one of the repos that were mirrored ended up having the mirror settings set. However, for the timer, it's set to 8h0m0s. Whereas my pull time in the docker yml is set to 30 minutes.

Is the pull time for docker only how often it looks for new repos? And then 8 hours to sync for each one? Or is this a bug?

@jaedle
Copy link
Owner

jaedle commented Oct 24, 2023

Hey 👋

First of all sorry for the late response. I am pretty busy with private manners right now.

This tool is only a small script to automatically create repositories on a specific Gitea instance which are mirrored from GitHub.
It’s literally just a replacement to the click through procedure to setup that manually on Gitea.

The synchronization method is completely implemented and handled by Gitea, you may have a look at their docs:
https://docs.gitea.com/usage/repo-mirror

The will absolutely work without the script running for already existing repo mirrors.

The script will run with a fixed delay, i.e. 8 hours. After 8 hours it may create new repository mirrors for added repositories on your GitHub user or organization.

If you have an error on your mirror refresh I would recommend to analyse the logs of your Gitea instance and probably open an issue on the Gitea repo.

Sorry again for the late response. I hope my answer was helpful to you.

Best,
Dennis

@jaedle
Copy link
Owner

jaedle commented Oct 24, 2023

In order to change the default mirror time (8 hours), it could be possible to introduce a configuration for a pull interval which could be overwritten according to your needs.

How soon do you need the mirror update?

@jaedle jaedle added enhancement New feature or request good first issue Good for newcomers question Further information is requested labels Oct 24, 2023
@Aetherinox
Copy link
Author

Hey,

It's ok, I sort of figured Gitea was the one handling the duration when I saw that they were all set to 8 hours.

It would be a cool feature, but the time-frame is really up to you. I just went in and adjusted the time down on a few repos because I update them so frequently. But there's really no rush on it, whenever you have time it would be a nice addition.

@jaedle jaedle added the help wanted Extra attention is needed label Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants