what is repopulse-dashboard fr?

RepoPulse Dashboard is a self-hosted web app for developers and DevOps teams who want to track software releases and manage files across several platforms from one place. The README describes it as a high performance dashboard built with attention to visual design as well as functionality, combining unified repository tracking with a file explorer that supports multiple protocols. On the release tracking side, it can follow version updates from Git, GitHub, GitLab, Gitea, Forgejo, Bitbucket, Codeberg and F-Droid. Repositories can be organized into nested categories up to five levels deep, and the app keeps a history of the last ten versions for each one. You can filter by operating system compatibility, by category, or with instant search, and switch between list, grid, bento and column layouts. The file explorer is a two panel manager that connects to local server drives, FTP and SFTP servers, SMB network shares, and WebDAV storage such as Nextcloud. It can also browse and preview files hosted on standard web servers. Supported file operations include copy, move, rename, delete, permission changes and SHA256 hash checks. Visually, the interface follows a design language similar to Microsoft's Fluent Design, with a glassmorphism style of blurred, semi transparent panels. Users can pick from built in themes or build custom ones with their own accent colors and blur levels, and can upload their own favicon and sidebar icons. The app also supports automatic backups of new releases, Discord and Slack webhook notifications, a persistent transfer log, and interface translations for more than fifteen regions. The frontend is built with React 18, Vite and TypeScript, using Framer Motion for animation and Recharts for statistics. The backend runs on Node.js with Express. Styling uses Tailwind CSS, and data is stored locally rather than in an external database. Setup requires Node.js 18 or later and npm 9 or later: you clone the repository, install dependencies with npm, and either run it in development mode or build it for production and start it with a Node server. The README states that data stays on your own server rather than being sent elsewhere, and that credentials for remote connections are encrypted at rest. GitHub personal access tokens can be added to raise API rate limits and access private repositories. The project is released under the Apache License 2.0.