Automatic Mirroring and some docker compose flags not working

[Tailscale-VPS]

My Docker compose

services:
  gitea-mirror:
    image: docker.gitea.com/gitea:1.24.4
    container_name: gitea-mirror
    security_opt:
      - no-new-privileges:true
    networks:
      - proxy
    environment:
      - USER_UID=1001
      - USER_GID=1001
      - GITEA__service__DISABLE_REGISTRATION=true
      - GITEA__service__REQUIRE_SIGNIN_VIEW=true
    volumes:
      - /home/ubuntu/docker/stacks/app-data/gitea-mirror:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    labels:
      - traefik.enable=true
      - traefik.http.routers.gitea-mirror-rtr.entrypoints=websecure
      - traefik.http.routers.gitea-mirror-rtr.rule=Host(`site.example.com`)
      - traefik.http.routers.gitea-mirror-rtr.middlewares=chain-authelia@file
      - traefik.http.routers.gitea-mirror-rtr.service=gitea-mirror-svc
      - traefik.http.services.gitea-mirror-svc.loadbalancer.server.port=3000
    restart: unless-stopped

  gitea-mirror-backend:
    image: ghcr.io/raylabshq/gitea-mirror:v3.2.6
    container_name: gitea-mirror-backend
    security_opt:
      - no-new-privileges:true
    networks:
      - proxy
    user: 1001:1001
    environment:
      - NODE_ENV=production
      - HOST=0.0.0.0
      - PORT=4321
      - DATABASE_URL=file:data/gitea-mirror.db
      - BETTER_AUTH_URL=https://site-backend.example.com
      - BETTER_AUTH_TRUSTED_ORIGINS=https://site-backend.example.com
      - BETTER_AUTH_SECRET={Secret-here}
      - ENCRYPTION_SECRET={Secret-here}
      - GITHUB_USERNAME=Tailscale-VPS
      - GITHUB_TOKEN={Secret-here}
      - GITHUB_TYPE=personal
      - PRIVATE_REPOSITORIES=true
      - PUBLIC_REPOSITORIES=true
      - INCLUDE_ARCHIVED=false
      - SKIP_FORKS=false
      - MIRROR_STARRED=true
      - STARRED_REPOS_ORG=starred
      - MIRROR_ORGANIZATIONS=true
      - PRESERVE_ORG_STRUCTURE=true
      - ONLY_MIRROR_ORGS=false
      - MIRROR_STRATEGY=preserve
      - SKIP_STARRED_ISSUES=false
      - GITEA_URL=http://gitea-mirror:3000
      - GITEA_TOKEN={Secret-here}
      - GITEA_USERNAME=homelab10400
      - GITEA_ORGANIZATION=github-mirrors
      - GITEA_ORG_VISIBILITY=public
      - GITEA_MIRROR_INTERVAL=8h
      - GITEA_LFS=false
      - GITEA_CREATE_ORG=true
      - GITEA_PRESERVE_VISIBILITY=true
      - GITEA_ADD_TOPICS=true
      - GITEA_TOPIC_PREFIX=gh-
      - GITEA_FORK_STRATEGY=full-copy
      - MIRROR_RELEASES=true
      - MIRROR_WIKI=true
      - MIRROR_METADATA=true
      - MIRROR_ISSUES=true
      - MIRROR_PULL_REQUESTS=true
      - MIRROR_LABELS=true
      - MIRROR_MILESTONES=true
      - SCHEDULE_ENABLED=true
      - SCHEDULE_INTERVAL=3600
      - SCHEDULE_CONCURRENT=false
      - SCHEDULE_BATCH_SIZE=10
      - SCHEDULE_PAUSE_BETWEEN_BATCHES=5000
      - SCHEDULE_RETRY_ATTEMPTS=3
      - SCHEDULE_RETRY_DELAY=60000
      - SCHEDULE_TIMEOUT=3600000
      - SCHEDULE_AUTO_RETRY=true
      - SCHEDULE_ONLY_MIRROR_UPDATED=false
      - SCHEDULE_UPDATE_INTERVAL=86400000
      - SCHEDULE_SKIP_RECENTLY_MIRRORED=true
      - SCHEDULE_RECENT_THRESHOLD=3600000
      - SCHEDULE_CLEANUP_BEFORE_MIRROR=false
      - SCHEDULE_LOG_LEVEL=info
      - SCHEDULE_TIMEZONE=Asia/Kolkata
      - CLEANUP_ENABLED=true
      - CLEANUP_RETENTION_DAYS=7
      - CLEANUP_DELETE_FROM_GITEA=true
      - CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
      - CLEANUP_ORPHANED_REPO_ACTION=archive
      - CLEANUP_DRY_RUN=false
      - CLEANUP_BATCH_SIZE=10
      - CLEANUP_PAUSE_BETWEEN_DELETES=2000
    volumes:
      - /home/ubuntu/docker/stacks/app-data/gitea-mirror-backend:/app/data
    labels:
      - traefik.enable=true
      - traefik.http.routers.gitea-mirror-backend-rtr.entrypoints=websecure
      - traefik.http.routers.gitea-mirror-backend-rtr.rule=Host(`site-backend.example.com`)
      - traefik.http.routers.gitea-mirror-backend-rtr.middlewares=chain-authelia@file
      - traefik.http.routers.gitea-mirror-backend-rtr.service=gitea-mirror-backend-svc
      - traefik.http.services.gitea-mirror-backend-svc.loadbalancer.server.port=4321
    healthcheck:
      test:
        [
          "CMD",
          "wget",
          "--no-verbose",
          "--tries=3",
          "--spider",
          "http://localhost:4321/api/health",
        ]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 15s
    depends_on:
      - gitea-mirror
    restart: unless-stopped

networks:
  proxy:
    external: true

Env Variables probably related to issue

      - GITEA_MIRROR_INTERVAL=8h
      - SCHEDULE_ENABLED=true
      - SCHEDULE_INTERVAL=3600
      - SCHEDULE_UPDATE_INTERVAL=86400000
      - SCHEDULE_SKIP_RECENTLY_MIRRORED=true
      - SCHEDULE_RECENT_THRESHOLD=3600000
      - CLEANUP_DELETE_FROM_GITEA=true
      - CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
      - CLEANUP_ORPHANED_REPO_ACTION=archive
      - CLEANUP_DRY_RUN=false

ISSUES
1 - The GITEA_MIRROR_INTERVAL=8h counts time from the container startup OR from the time the repo was mirrored? Because as you can see i have mirrored the repos at August 9, 2025 at 11:00 PM and the container was restarted at August 10, 2025 at 04:00 AM. Till now there was no logs of mirroring again.Even when -SCHEDULE_INTERVAL=3600

Reason - Probably because of ?
- SCHEDULE_UPDATE_INTERVAL=86400000
- SCHEDULE_SKIP_RECENTLY_MIRRORED=true
- SCHEDULE_RECENT_THRESHOLD=3600000

2 - I have removed star from the winlator repo yesterday but its still not deleted from gite/gitea-mirror. Even though these flags are there
- CLEANUP_DELETE_FROM_GITEA=true
- CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
- CLEANUP_ORPHANED_REPO_ACTION=archive
- CLEANUP_DRY_RUN=false

Reason - Same as for 1

After Solving the above, I believe you can aslo close #50

[Tailscale-VPS]

UPDATE
It's been more than 24hr's that repo's was clonned and winlator was removed from starred from github, Still no automatic mirror/delete ran after that.

So it's probably not the flags

• SCHEDULE_UPDATE_INTERVAL=86400000
• SCHEDULE_SKIP_RECENTLY_MIRRORED=true
• SCHEDULE_RECENT_THRESHOLD=3600000

Container restarts at 4.00 AM IST

LOGS AFTER RESTART TILL NOW

gitea-mirror-backend-2025-08-11T12-04-47.log

[arunavo4]

@Tailscale-VPS Thank you for the detailed logs and info. I will test and fix this today.

[arunavo4]

@Tailscale-VPS Have a look at v3.3.0

[Tailscale-VPS]

Sure ill test in within 24hrs.

[Tailscale-VPS]

@arunavo4 Here are the new findings

Docker compose ENV used -

      - SCHEDULE_ENABLED=true
      - SCHEDULE_INTERVAL=300
      - SCHEDULE_CONCURRENT=true
      - SCHEDULE_BATCH_SIZE=5
      - SCHEDULE_PAUSE_BETWEEN_BATCHES=5000
      - SCHEDULE_RETRY_ATTEMPTS=3
      - SCHEDULE_RETRY_DELAY=60000
      - SCHEDULE_TIMEOUT=3600000
      - SCHEDULE_AUTO_RETRY=true
      - SCHEDULE_ONLY_MIRROR_UPDATED=false
      - SCHEDULE_UPDATE_INTERVAL=300000
      - SCHEDULE_SKIP_RECENTLY_MIRRORED=true
      - SCHEDULE_RECENT_THRESHOLD=3600000
      - SCHEDULE_CLEANUP_BEFORE_MIRROR=true
      - SCHEDULE_NOTIFY_ON_FAILURE=true
      - SCHEDULE_NOTIFY_ON_SUCCESS=false
      - SCHEDULE_LOG_LEVEL=infoaking it as 
      - SCHEDULE_TIMEZONE=Asia/Kolkata
      - CLEANUP_ENABLED=true
      - CLEANUP_RETENTION_DAYS=7
      - CLEANUP_DELETE_FROM_GITEA=true
      - CLEANUP_DELETE_IF_NOT_IN_GITHUB=true
      - CLEANUP_ORPHANED_REPO_ACTION=archive
      - CLEANUP_DRY_RUN=false
      - CLEANUP_BATCH_SIZE=10
      - CLEANUP_PAUSE_BETWEEN_DELETES=2000

The sync is running at every 5min which is correct but then update interval value which it should also take 5min is not working correctly .

• It's automatically taking/changing it as 24 hr. (Probably because visitiing the UI changes the value and UI variable value is > value set in compose ENV varibale)

• Even if i set it to 1hr from the ui , It's functioning is not correct -
  It's counting the time from the last sync happened for eg is last sync is at 4.00 PM then update should be at 5.00 PM but a bit later last sync will be at 4.05 PM then the update is also changig to 5.05 PM.
  Considering the above the update will never happen until sync interval is > update interval.

• I have tried removing satrred repo from github , but i dont know will it be removed from the mirror when the sync runs or when the update runs.
  If its deleted when the sync runs then its not working.
  If its when the update runs , then ill wait cuz the update part is a bit broken currently.

Questions/Suggestion

• I beleive your are checking for the repos user have forked,starred,etc in its github and matching them to mirror when the update runs?
  If thats right the will it also pick up new starred,forked repos automatically when it runs update?
  If YES, then i will like to point out that when new repos are found (tested from clean setup and clicking on import from github) and if sync happens, then it will do noting because they are not mirrored yet, I don't know if itts a bug or not yet implemented.
  IN SHORT USER HAVE TO CLICK MIRROR FOR EVERY NEW REPO SO THAT MIRROR FUNCTION CORRECTLY

• It's a minor thing but if say the above is not a bug and u were going to implemet it correctly then i would suggest to add a variable for Import from github also , currently even after setting up everything as ENV in compose , the user still needs to click on Import from github else repos will not come.

Ideally what should have happenned -

After initial setup,user should just need to do things with its github only, like fork,star new repos or remove old repos from starred.
In backend gitea mirror should do rest of the work like importing github repos and sync to gitea using compose parameters.

Log snippet if required -

Starting automatic mirror scheduler service...
[Scheduler] Starting scheduler service
[Scheduler] Scheduler service started, checking every 1m for scheduled tasks
[Scheduler] To trigger manual sync, check your configuration intervals and ensure SCHEDULE_ENABLED=true or use GITEA_MIRROR_INTERVAL
Starting repository cleanup service...
[Repository Cleanup] Starting repository cleanup service
[Repository Cleanup] Service started, checking every 6 hours
[Scheduler] No configurations with scheduling enabled (found 0 active configs)
[Repository Cleanup] No configurations with repository cleanup enabled
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI - next run at 2025-08-29T10:04:20.906Z
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI - next run at 2025-08-29T10:04:20.906Z
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */0 * * *
[Scheduler] Parsed interval "0 */0 * * *" as 0ms
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-29T10:01:53.647Z (in 0ms)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 2 * * *
[Scheduler] Parsed interval "0 2 * * *" as 1d
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-30T10:02:53.648Z (in 1d)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Starting automatic cleanup service...
Running cleanup for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI with 7 days retention (604800 seconds)
Cleanup completed for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 events, 0 jobs deleted
Updated cleanup config for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI, next run: 2025-08-30T10:03:53.645Z (24h interval for 7d retention)
Automatic cleanup completed. Processed 1 users.
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-30T10:03:53.652Z (in 1d)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-30T10:04:53.654Z (in 1d)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
🛑 Received shutdown signal, forwarding to application...
📡 Received SIGTERM signal
🛑 Graceful shutdown initiated by signal: SIGTERM
📊 Shutdown status: 0 active jobs, 3 callbacks
📝 Step 1: Saving active job states...
No active jobs to save
🔧 Step 2: Executing shutdown callbacks...
Executing 3 shutdown callbacks...
🛑 Shutting down cleanup service...
🛑 Stopping cleanup service...
✅ Cleanup service stopped
🛑 Shutting down scheduler service...
[Scheduler] Scheduler service stopped
🛑 Shutting down repository cleanup service...
[Repository Cleanup] Service stopped
✅ Shutdown callback 1 completed
✅ Shutdown callback 2 completed
✅ Shutdown callback 3 completed
✅ Completed all shutdown callbacks
💾 Step 3: Closing database connections...
✅ Graceful shutdown completed successfully
No custom CA certificates found in /app/certs
System CA bundle mounted, configuring Node.js to use it...
NODE_EXTRA_CA_CERTS set to: /etc/ssl/certs/ca-certificates.crt
Database already exists, checking for issues...
🔧 Fixing database location issues...
✅ Database location fixed
Database exists, checking integrity...
Setting application version: 3.3.0
Checking for environment configuration...
Loading configuration from environment variables...
Successfully connected to SQLite database using Bun's native driver
🔄 Checking for pending migrations...
✅ Database migrations completed successfully
=== Gitea Mirror Environment Configuration ===
Loading configuration from environment variables...
[ENV Config Loader] Found environment configuration, initializing...
[ENV Config Loader] Updating existing configuration with environment variables
[ENV Config Loader] Configuration initialized successfully from environment variables
✅ Environment configuration loaded successfully in 49ms
✅ Environment configuration loaded successfully
Running startup recovery...
Running startup recovery using compiled script...
Successfully connected to SQLite database using Bun's native driver
🔄 Checking for pending migrations...
✅ Database migrations completed successfully
=== Gitea Mirror Startup Recovery ===
Timeout: 30000ms
Force recovery: false
Checking if recovery is needed...
✅ No jobs need recovery. Startup can proceed.
✅ Startup recovery completed successfully
Running repository status repair...
Running repository repair using compiled script...
Successfully connected to SQLite database using Bun's native driver
🔄 Checking for pending migrations...
✅ Database migrations completed successfully
Repair process complete.
✅ Repository status repair completed successfully
Starting Gitea Mirror...
10:05:22 [@astrojs/node] Server listening on 
  local: https://localhost:4321 	
  network: https://172.19.0.16:4321/
Successfully connected to SQLite database using Bun's native driver
🔄 Checking for pending migrations...
✅ Database migrations completed successfully
🔧 Initializing shutdown manager and signal handlers...
🔧 Initializing shutdown manager...
✅ Shutdown manager initialized
🔧 Setting up signal handlers for graceful shutdown...
✅ Signal handlers registered successfully
✅ Shutdown manager and signal handlers initialized
[ENV Config Loader] Found environment configuration, initializing...
[ENV Config Loader] Updating existing configuration with environment variables
[ENV Config Loader] Configuration initialized successfully from environment variables
✅ No recovery needed (startup script likely handled it)
Starting automatic database cleanup service...
Starting background cleanup service...
✅ Cleanup service started. Will run every 60 minutes.
Starting automatic mirror scheduler service...
[Scheduler] Starting scheduler service
[Scheduler] Scheduler service started, checking every 1m for scheduled tasks
[Scheduler] To trigger manual sync, check your configuration intervals and ensure SCHEDULE_ENABLED=true or use GITEA_MIRROR_INTERVAL
Starting repository cleanup service...
[Repository Cleanup] Starting repository cleanup service
[Repository Cleanup] Service started, checking every 6 hours
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 300
[Scheduler] Parsed interval "300" as 5m
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-29T10:10:26.935Z (in 5m)
[Repository Cleanup] Processing 1 configurations
[Repository Cleanup] Starting repository cleanup for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Repository Cleanup] No orphaned repositories found for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Publishing event to channel mirror-status:JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Publishing event to channel mirror-status:JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Event published successfully with ID 21fa7afa-ef79-4207-a90b-63bb3e5af413
Event published successfully with ID b43261e9-060e-420e-b594-5f2f2950527d
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-30T10:06:26.933Z (in 1d)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-30T10:07:26.934Z (in 1d)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI - next run at 2025-08-30T10:07:26.934Z
Job 93f15e5d-08a0-4bc9-b665-5d093be2a0b5 has no log data
Job 6cd18a8b-d6d4-47e7-b7f7-1f38f58dc8b7 has no log data
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-30T10:09:26.936Z (in 1d)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Publishing event to channel mirror-status:JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Event published successfully with ID 5eec4545-6da5-4c0f-9eac-8130bb6af278
Created new job c927ae00-987c-4b21-a0f4-55f61fcb3de0 with 2 items
Registered active job: c927ae00-987c-4b21-a0f4-55f61fcb3de0 (1 total active jobs)
Starting mirror for repository: AdrenoToolsDrivers

[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */1 * * *
[Scheduler] Parsed interval "0 */1 * * *" as 1h
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-29T11:22:26.964Z (in 1h)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Publishing event to channel mirror-status:JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
Event published successfully with ID 3c051f2f-c278-417e-95b6-58973c1a28d8
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Using interval source for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI: 0 */1 * * *
[Scheduler] Parsed interval "0 */1 * * *" as 1h
[Scheduler] Next sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI scheduled for: 2025-08-29T11:23:26.966Z (in 1h)
[Scheduler] No repositories to sync for user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user JWfDpcgqdR6xvQEGAdQ3IhnferRmEQQI - next run at 2025-08-29T11:23:26.966Z
Job 93f15e5d-08a0-4bc9-b665-5d093be2a0b5 has no log data
Job 6cd18a8b-d6d4-47e7-b7f7-1f38f58dc8b7 has no log data
Job c927ae00-987c-4b21-a0f4-55f61fcb3de0 has no log data
Job 8832a14b-54d7-4828-b39b-00e3263cc1be has no log data
Job 4a29014a-6dd0-421f-b42b-becd2532cefa has no log data

[arunavo4]

@Tailscale-VPS Looking into it, also what is the screen resolution of this android tablet I am guessing?. I want to optimse the UI better.

[Tailscale-VPS]

@Tailscale-VPS Looking into it, also what is the screen resolution of this android tablet I am guessing?. I want to optimse the UI better.

Yes its a Tab
Aspect Ratio - 7:5
Resolution- 3000 x 2120 (303 PPI)

[arunavo4]

@Tailscale-VPS Try v3.5.0 I have updated the UI and also your automation stuff, taken all your suggestions.

[Tailscale-VPS]

@arunavo4 checked v3.5.0 UI looks good and here is what i have found -

• The Auto import is working as expected (Even tested 2-3 times again and again, it works fine for initial setup and also when the schedular runs)

• Auto mirroring still not works , So repos are stuck to imported only.

• Schedular logic seems to work fine now (Also in logs u can see it tries to delete the winlator repo when schedular runs so i believe the delete functionality is also working fine, ignore the errors those are there because there was no repo named winlator in gitea as it was not mirrored)

• Talking about the Scheduling time,It's not working correctly.It still has same issue and i think i found out why it's behaving this way.

What is happenning
After the initial setup using compose variables it will work fine as long as the user has not visited the configuration page from the UI.
What happens is as u are using UI values preference > Compose ENV, and you have also defined default vaules for sync and database cleanup in UI (Daily and Weekly).
The compose Env is getting overidden when the user visits the UI configuration page (You can see in log2 or in the Screenshots)

Why does this not happen earlier
The reason is simple, because other settings were blank and there were no default prefilled values, and after taking the compose env values , The UI values becomes = Compose ENV values , so no issue happens.

Suggestion
We can either remove default value from the Automation part of the UI OR we need to put a custom option there so that default value = Custom ,
And the custom value either user can put through UI or it will be filled directly through compose ENV like rest of the values.

gitea-mirror-backend-2025-08-29T17-46-11.log

gitea-mirror-backend-2025-08-29T17-57-23.log

[arunavo4]

@Tailscale-VPS thanks for the detailed info. Btw there is no automatic mirroring at the start. You need to first mirror the repos and only then automatic mirroring starts. Okay maybe now I understand the confusion I should change it to automatic syncing sorry for wording it wrong.

But you need to first start the mirroring manually using either mirror all button or mirroring them one by one. The reason this is done so that people who don't want to mirror certain repos can skip repos and do all that so that automatic syncing can start.

[arunavo4]

@Tailscale-VPS v3.5.1

• Fixed scheduling configuration being overridden by UI defaults when loading the config page, preserving ENV variable values correctly
• Updated UI text from "Automatic Mirroring" to "Automatic Syncing" to clarify that this feature only synchronizes already-mirrored repositories

[Tailscale-VPS]

@Tailscale-VPS v3.5.1

• Fixed scheduling configuration being overridden by UI defaults when loading the config page, preserving ENV variable values correctly
• Updated UI text from "Automatic Mirroring" to "Automatic Syncing" to clarify that this feature only synchronizes already-mirrored repositories

• Still getting overridden i believe.

Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Using interval source for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ: 300
[Scheduler] Parsed interval "300" as 5m
[Scheduler] Next sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ scheduled for: 2025-08-29T20:21:56.409Z (in 5m)
[Scheduler] Checking for new GitHub repositories for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ...
[Scheduler] Found 2 new repositories for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Successfully imported 2 new repositories for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Checking for orphaned repositories to cleanup for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ...
[Scheduler] No orphaned repositories found for cleanup
[Scheduler] No repositories to sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
 
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Skipping user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ - next run at 2025-08-29T20:21:56.409Z
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Using interval source for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ scheduled for: 2025-08-30T20:19:56.411Z (in 1d)
[Scheduler] Checking for new GitHub repositories for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ...
[Scheduler] No new repositories found for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Checking for orphaned repositories to cleanup for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ...
[Scheduler] No orphaned repositories found for cleanup
[Scheduler] No repositories to sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Using interval source for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ scheduled for: 2025-08-30T20:20:56.412Z (in 1d)
[Scheduler] Checking for new GitHub repositories for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ...
[Scheduler] No new repositories found for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Checking for orphaned repositories to cleanup for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ...
[Scheduler] No orphaned repositories found for cleanup
[Scheduler] No repositories to sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Processing 1 configurations with scheduling enabled (out of 1 total active configs)
[Scheduler] Running scheduled sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ
[Scheduler] Using interval source for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ: 0 */24 * * *
[Scheduler] Parsed interval "0 */24 * * *" as 1d
[Scheduler] Next sync for user 7z4cI3hAJONA7MWQ8XnFuikTtcMi2ztZ scheduled for: 2025-08-30T20:21:56.414Z (in 1d)