Releases: 666mxvbee/LinkTrackerBot
Releases · 666mxvbee/LinkTrackerBot
1.1.0 - PostgreSQL Storage and Scheduled Updates
Summary
This release adds persistent PostgreSQL storage and scheduled link update processing to LinkTracker.
Scrapper now stores chats, links, subscriptions, and tags in PostgreSQL, supports both raw SQL and EF Core repository implementations, applies SQL migrations on startup, and checks GitHub/StackOverflow links for updates on a schedule.
Highlights
- Added PostgreSQL persistence for Scrapper data.
- Added SQL migrations with DbUp.
- Added Docker Compose PostgreSQL setup.
- Added raw SQL repositories using Npgsql.
- Added ORM repositories using EF Core.
- Added configurable database access mode:
SQLorORM. - Added tag CRUD and tag-based link filtering.
- Added scheduled update checks for tracked links.
- Added GitHub issue and pull request update detection.
- Added StackOverflow answer and comment update detection.
- Added batched and parallel link processing.
- Added HTTP notification sender from Scrapper to Bot.
- Added Testcontainers and WireMock-based tests.
- Updated README with setup instructions and project badges.
Verification
dotnet restoredotnet builddotnet testdocker compose up --build
1.0.2
1.0.1
1.0.0
Overview
First stable release of the LinkTracker System. The project is now fully containerized and ready for deployment.
Key Features
- Microservices Architecture: Separate services for Bot logic and Link Scrapping.
- Docker Integration: Full support for
docker-composewith automated infrastructure setup. - Telegram Bot: Added
/start,/help,/track, and/listcommands. - Real-time Monitoring: Scrapper service monitors GitHub and StackOverflow via Quartz scheduler.
Improvements & Fixes
- CI/CD: Added GitHub Actions workflow for Docker builds.
- Environment: Moved sensitive data (Bot Token) to
.envfiles. - Migration: Ported the entire solution to .NET 9.0.
How to run
- Clone the repository.
- Create a
.envfile with yourTELEGRAM_BOT_TOKEN. - Run
docker-compose up --build.
