Can't backup clickhouse database

To Reproduce

1. Create Plausible service from template
2. Go to "Backups" tab
3. Try to backup clickhouse DB with event data

Current vs. Expected behavior

Expected behavior

My expectation is i can pick container and volumes to backup

Actual behavior

UI is a mess, it is absolutely not clear what i can backup. Docks have no information about it too.

It looks i can backup only databases that is pointless in my case.

I can't backup clickhouse database, since it is missed in list of databases

Provide environment information

OS: Ubuntu 24.04

Which area(s) are affected? (Select all that apply)

Databases

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

I'm not sure it is good idea to limit user to backup only databases.

Because of current approach, as user I limited to use Dokploy only as service to host static sites, since i can't trust to a service where i can't even manage my data.

I have Plausible instance on my another server and i just tried to migrate data to Dokploy.
That is not possible, because there are no feature to manage volumes.

I can manually log in via SSH to copy directories from server A to server B, then configure docker compose file to use directory like /data/plausible/clickhouse as volume, but i can't setup Dokploy to manage backups, so as result i just waste time.

My expectation is Dokploy will

• provide service to deploy my projects (including via CLI as heroku does)
• provide powerful management for backups

Both expectations is false for now. It is unclear what is purpose of Dokploy then. It have nice UI, and at least it started well unlike Coolify, but this solution have no foundation features.

I hope you guys will think about core features and will make more attention on it.

Will you send a PR to fix it?

Maybe, need help

The issue does not identify implementation files, entry points, or tests for backup selection. Start by locating the Backups tab and the database backup flow, then determine how ClickHouse containers and volumes are represented; done should include a clear way to select and back up the requested data, with tests covering the new option.