Hi everyone,
I’d like to share some challenges I'm facing regarding backup management via the Ploi API and suggest a few improvements.
Currently, I manage hundreds of sites. Each site has 4 backups configured (2 for files, 2 for databases - both daily and monthly). Managing this scale purely through the API is quite difficult. To analyze which backups exist, which are missing, or to check their scheduled times (which is crucial for spreading the server load), I have to loop through all pages of the global backups endpoint. This results in an excessive number of API requests.
Here is what would make API management much more efficient:
1. API Enhancements (High Priority for My Workflow)
-
Support for per_page parameter: It would be awesome to control pagination, ideally allowing up to 50–100 items per page.
-
Server and Site Filters: Instead of fetching all backups globally, it would be a game-changer to have dedicated endpoints or filters, such as:
/api/servers/{server_id}/backups/(file|database)/api/servers/{server_id}/sites/{site_id}/backups/(file|database)
This would allow us to quickly pinpoint the exact backups we need and then interact with them using the existing endpoints (like /api/backups/file/{id}).
2. UI/UX Improvements (Nice to have)
- Dashboard Filters: In the Ploi panel under the Backups section, there is a "Servers" column, but no way to filter by a specific server or site. Adding a dropdown filter here would make manual management much easier when dealing with a large fleet of servers.
- File Backups Popup & Downloads: For Database backups, we have a handy popup showing existing files. It would be great to have the same popup for File backups. Even better - a button to download the backup directly (e.g., by generating a temporary/presigned AWS URL, if technically feasible).
Curious to hear your thoughts on this. Thanks for the awesome tool!
