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?
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?
<!-- github-sync-id:3073632901 -->
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.
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.
<!-- github-comment-id:2890845058 -->
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 ^^
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 ^^
<!-- github-comment-id:2890850314 -->
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.
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.
<!-- github-comment-id:2897050628 -->
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.
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?
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.
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 ^^
You can use a common redis that you may use for other things also. Say for other apps for now.
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.
Awesome!