Bugs observered #25

New Issue

GiteaMirror · 2025-10-31T15:27:59-05:00

GiteaMirror commented

2025-10-31 15:27:59 -05:00

Originally created by @dot-mike on GitHub (Jul 19, 2025).

I just finished setting up this in my own environment. And I observed some bugs:

Starred mirrors get into wrong organization. Expected org: dot-mike-starred actually org: starred. All I did was specify the new org and click "import github data" followed by mirroring A SINGLE repo for testing: 7x50_YangModels which I expected to go into org dot-mike-starred
Unable to configure Enable automatic database cleanup. Whenever I set another time in the dropdown for Data retention period it always selects 1 week.
Mirroring from org that I'm part of causes the mirror to into my personal profile on Gitea. Repo amfphp-2.0 was expected to go into team specific repo.

Settings:

Originally created by @dot-mike on GitHub (Jul 19, 2025). I just finished setting up this in my own environment. And I observed some bugs: - Starred mirrors get into wrong organization. Expected org: dot-mike-starred actually org: `starred`. All I did was specify the new org and click "import github data" followed by mirroring A SINGLE repo for testing: `7x50_YangModels` which I expected to go into org `dot-mike-starred` - Unable to configure `Enable automatic database cleanup`. Whenever I set another time in the dropdown for `Data retention period` it always selects `1 week`. - Mirroring from org that I'm part of causes the mirror to into my personal profile on Gitea. Repo `amfphp-2.0` was expected to go into team specific repo. Settings: <img width="3391" height="1813" alt="Image" src="https://github.com/user-attachments/assets/16f35ea3-2452-47ce-8067-c116eae87a5f" /> <img width="876" height="475" alt="Image" src="https://github.com/user-attachments/assets/f4cd57c8-4a1a-4105-a4fc-31cfd8972cdd" />

GiteaMirror closed this issue

2025-10-31 15:27:59 -05:00

GiteaMirror commented

2025-10-31 15:27:59 -05:00

@dot-mike commented on GitHub (Jul 19, 2025):

I did a complete re-install (deleting DB ofc). Sharing my docker-config below. Same issue experienced

services:
  gitea-mirror:
    image: ghcr.io/raylabshq/gitea-mirror:v3.0.1
    container_name: gitea-mirror
    restart: unless-stopped
    user: 1026:100
    ports:
      - "4321:4321"
    volumes:
      - /volume2/docker/gitmirror/data:/app/data
      - /volume2/docker/gitmirror/certs:/app/certs
    environment:
      - TZ=Europe/Berlin
      - NODE_ENV=production
      - DATABASE_URL=file:data/gitea-mirror.db
      - HOST=0.0.0.0
      - PORT=4321
      - BETTER_AUTH_SECRET=<secret>
      - BETTER_AUTH_URL=<secret>
      - ENCRYPTION_SECRET=<secret>
      - GITHUB_USERNAME=dot-mike
      - GITHUB_TOKEN=<secret>
      - GITEA_URL=<secret>
      - GITEA_TOKEN=<secret>
      - GITEA_USERNAME=<secret>
      - DELAY=${DELAY:-3600}
      # Optional: Skip TLS verification (insecure, use only for testing)
      # - GITEA_SKIP_TLS_VERIFY=${GITEA_SKIP_TLS_VERIFY:-false}
      # Header Authentication (for Reverse Proxy SSO)
      - HEADER_AUTH_ENABLED=${HEADER_AUTH_ENABLED:-false}
      - HEADER_AUTH_USER_HEADER=${HEADER_AUTH_USER_HEADER:-X-Authentik-Username}
      - HEADER_AUTH_EMAIL_HEADER=${HEADER_AUTH_EMAIL_HEADER:-X-Authentik-Email}
      - HEADER_AUTH_NAME_HEADER=${HEADER_AUTH_NAME_HEADER:-X-Authentik-Name}
      - HEADER_AUTH_AUTO_PROVISION=${HEADER_AUTH_AUTO_PROVISION:-false}
      - HEADER_AUTH_ALLOWED_DOMAINS=${HEADER_AUTH_ALLOWED_DOMAINS:-}
      - NODE_TLS_REJECT_UNAUTHORIZED=0

@dot-mike commented on GitHub (Jul 19, 2025): I did a complete re-install (deleting DB ofc). Sharing my docker-config below. Same issue experienced ``` services: gitea-mirror: image: ghcr.io/raylabshq/gitea-mirror:v3.0.1 container_name: gitea-mirror restart: unless-stopped user: 1026:100 ports: - "4321:4321" volumes: - /volume2/docker/gitmirror/data:/app/data - /volume2/docker/gitmirror/certs:/app/certs environment: - TZ=Europe/Berlin - NODE_ENV=production - DATABASE_URL=file:data/gitea-mirror.db - HOST=0.0.0.0 - PORT=4321 - BETTER_AUTH_SECRET=<secret> - BETTER_AUTH_URL=<secret> - ENCRYPTION_SECRET=<secret> - GITHUB_USERNAME=dot-mike - GITHUB_TOKEN=<secret> - GITEA_URL=<secret> - GITEA_TOKEN=<secret> - GITEA_USERNAME=<secret> - DELAY=${DELAY:-3600} # Optional: Skip TLS verification (insecure, use only for testing) # - GITEA_SKIP_TLS_VERIFY=${GITEA_SKIP_TLS_VERIFY:-false} # Header Authentication (for Reverse Proxy SSO) - HEADER_AUTH_ENABLED=${HEADER_AUTH_ENABLED:-false} - HEADER_AUTH_USER_HEADER=${HEADER_AUTH_USER_HEADER:-X-Authentik-Username} - HEADER_AUTH_EMAIL_HEADER=${HEADER_AUTH_EMAIL_HEADER:-X-Authentik-Email} - HEADER_AUTH_NAME_HEADER=${HEADER_AUTH_NAME_HEADER:-X-Authentik-Name} - HEADER_AUTH_AUTO_PROVISION=${HEADER_AUTH_AUTO_PROVISION:-false} - HEADER_AUTH_ALLOWED_DOMAINS=${HEADER_AUTH_ALLOWED_DOMAINS:-} - NODE_TLS_REJECT_UNAUTHORIZED=0 ```

GiteaMirror commented

2025-10-31 15:28:00 -05:00

@arunavo4 commented on GitHub (Jul 19, 2025):

@dot-mike Thanks for reporting the issues. I think I may have left some default values somewhere. will search and fix it

@arunavo4 commented on GitHub (Jul 19, 2025): @dot-mike Thanks for reporting the issues. I think I may have left some default values somewhere. will search and fix it

GiteaMirror commented

2025-10-31 15:28:01 -05:00

@arunavo4 commented on GitHub (Jul 21, 2025):

@dot-mike please try the latest release v3.1.0

@arunavo4 commented on GitHub (Jul 21, 2025): @dot-mike please try the latest release v3.1.0

GiteaMirror commented

2025-10-31 15:28:02 -05:00

@arunavo4 commented on GitHub (Aug 29, 2025):

@dot-mike Feel free to reopen issue if it still exists but i have tested it and its fixed

@arunavo4 commented on GitHub (Aug 29, 2025): @dot-mike Feel free to reopen issue if it still exists but i have tested it and its fixed

GiteaMirror referenced this issue

2026-04-11 09:02:01 -05:00