feat: Refactor database cleanup process by removing scripts and updating documentation to use the Activity Log for event management

src/content/docs/configuration.md

@@ -150,20 +150,11 @@ Events in Gitea Mirror (such as repository mirroring operations) are stored in t
 # View all events in the database
 bun scripts/check-events.ts
 
-# Clean up old events (default: older than 7 days)
-bun scripts/cleanup-events.ts
-
-# Clean up old mirror jobs (default: older than 7 days)
-bun scripts/cleanup-mirror-jobs.ts
-
-# Clean up both events and mirror jobs
-bun run cleanup-all
-
 # Mark all events as read
 bun scripts/mark-events-read.ts
 ```
 
-When using Docker, database cleanup is automatically scheduled to run daily. You can customize the retention periods by setting the `EVENTS_RETENTION_DAYS` and `JOBS_RETENTION_DAYS` environment variables in your docker-compose file.
+For cleaning up old activities and events, use the cleanup button in the Activity Log page of the web interface.
 
 ### Health Check Endpoint
 

src/content/docs/quickstart.md

@@ -179,4 +179,4 @@ After your initial setup:
 - Check out the [Configuration Guide](/configuration) for advanced settings
 - Review the [Architecture Documentation](/architecture) to understand the system
 - For server deployments, set up monitoring using the health check endpoint
-- Consider setting up a cron job to clean up old events: `bun scripts/cleanup-events.ts`
+- Use the cleanup button in the Activity Log page to manage old events and activities

src/lib/events.ts

@@ -214,7 +214,7 @@ export async function removeDuplicateEvents(userId?: string): Promise<{ duplicat
 
 /**
  * Cleans up old events to prevent the database from growing too large
- * Should be called periodically (e.g., daily via a cron job)
+ * This function is used by the cleanup button in the Activity Log page
  *
  * @param maxAgeInDays Number of days to keep events (default: 7)
  * @param cleanupUnreadAfterDays Number of days after which to clean up unread events (default: 2x maxAgeInDays)