It seems the releases are affected too with wrong sort order. The earlier release is on top while the newer release is on second.
It seems the releases are affected too with wrong sort order. The earlier release is on top while the newer release is on second.
<img width="202" height="1171" alt="Image" src="https://github.com/user-attachments/assets/973dab86-fe0c-445a-9003-370945299a72" />
<!-- github-sync-id:3550178006 -->
One question in offtopic. What config has the priority? The config file or the gui changes? I use a lxc from helper-scripts, so no docker.
thanks for the fast response.
One question in offtopic. What config has the priority? The config file or the gui changes? I use a lxc from helper-scripts, so no docker.
<!-- github-comment-id:3444003198 -->
@Just4Link the Env variables or config files only will load at the first start of the application onto the SQLite db that will store all the user pref and that shows in GUI and if you change anything on the web GUI that then is stored in db and considered latest update or source of truth
@Just4Link the Env variables or config files only will load at the first start of the application onto the SQLite db that will store all the user pref and that shows in GUI and if you change anything on the web GUI that then is stored in db and considered latest update or source of truth
<!-- github-comment-id:3444297010 -->
@Just4Link It will be released in the next release for now you can test this image docker pull ghcr.io/raylabshq/gitea-mirror:af9bc86 and close the issue if its working as expected.
@Just4Link It will be released in the next release for now you can test this image `docker pull ghcr.io/raylabshq/gitea-mirror:af9bc86` and close the issue if its working as expected.
<!-- github-comment-id:3449319656 -->
I dont use a docker instance. I run gitea-mirror in a lxc from the community-scripts. But of course i give feedback asap when the new version is out.
I dont use a docker instance. I run gitea-mirror in a lxc from the community-scripts. But of course i give feedback asap when the new version is out.
<!-- github-comment-id:3449992790 -->
I tested the new version 3.8.11. I mirrored the repository from above from scratch but the version are still not in the right order. Same behavior like on the screenshot in the first post.
I tested the new version 3.8.11. I mirrored the repository from above from scratch but the version are still not in the right order. Same behavior like on the screenshot in the first post.
<!-- github-comment-id:3467642596 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It seems the releases are affected too with wrong sort order. The earlier release is on top while the newer release is on second.
@Just4Link OKay will fix this tomorrow.
thanks for the fast response.
One question in offtopic. What config has the priority? The config file or the gui changes? I use a lxc from helper-scripts, so no docker.
@Just4Link the Env variables or config files only will load at the first start of the application onto the SQLite db that will store all the user pref and that shows in GUI and if you change anything on the web GUI that then is stored in db and considered latest update or source of truth
@Just4Link It will be released in the next release for now you can test this image
docker pull ghcr.io/raylabshq/gitea-mirror:af9bc86and close the issue if its working as expected.I dont use a docker instance. I run gitea-mirror in a lxc from the community-scripts. But of course i give feedback asap when the new version is out.
I tested the new version 3.8.11. I mirrored the repository from above from scratch but the version are still not in the right order. Same behavior like on the screenshot in the first post.