mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-03-11 08:14:25 -05:00
[Feature Request] Run without redis #2
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea-mirror#2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CrazyWolf13 on GitHub (May 19, 2025).
Hi
I really love this app and the concept behind it, but I don't really like the idea of running a full redis container just for a UI which basically only tells my forgejo instance to mirror a project. Is there any possibility to directly bundle it or leave it out fully?
Maybe a local db-file would be more appropriate?
@arunavo4 commented on GitHub (May 19, 2025):
Hi @CrazyWolf13 Redis is used for job queuing and real-time updates, not just for storage. While we already use SQLite for persistent data. But I understand your concern maybe we can have an alternative lite mode where we use sqlite for eveyrthing but we end up loosing the realtime updates and would have to switch to polling it on intervals.
@CrazyWolf13 commented on GitHub (May 19, 2025):
Ahh I see, thanks for the explanation!
Yeah it's not that I wouldn't have the ressources, but I feel like for an app that esentially only tells my forgejo to start mirroring process it's a bit heavy in comparison ^^
@arunavo4 commented on GitHub (May 19, 2025):
You can use a common redis that you may use for other things also. Say for other apps for now.
@arunavo4 commented on GitHub (May 21, 2025):
Hi @CrazyWolf13 I have reconsidered the use of redis and have removed it from the project. The app currently now uses a 5 sec polling for events. Also has a cron job for cleaning up very old events for maintainence. SInce there is no redis this is a trade off.
@CrazyWolf13 commented on GitHub (May 21, 2025):
Awesome!