Filter the Deployments table by server
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
When you run Dokploy with multiple servers, it is hard to see at a glance what is deployed on a given server. The global Deployments page (/dashboard/deployments) already shows a Server column and lets you search, filter by status, and filter by type, but there is no way to narrow the list down to a single server. To answer the question "what is running on server X?" you currently have to scan every row by eye or open each project and environment one by one.
Describe the solution you'd like
Add a "Server" filter dropdown to the Deployments table, next to the existing Status and Type filters. It would list every server that appears in the current deployments (plus an "All servers" default and a "Dokploy" entry for services that run on the local Dokploy host). Selecting a server filters the table to only the deployments running on it.
The Server column in this table is already sortable by clicking its header, so combined with the new filter you can both group everything by server and zoom into a single one.
Describe alternatives you've considered
- Using the existing free text search and typing a server name. This works in a basic way but is not discoverable, does not give you the list of available servers, and matches substrings across other columns.
- Opening each project and environment, where a per environment server filter already exists. This does not give a cross project view of a whole server.
- A dedicated "services by server" page or expandable cards on the Servers settings page. These are heavier additions, while the Deployments table already joins and displays all the data needed.
Additional context
The data is already available client side from the deployment.allCentralized query, which returns the server for each deployment, so this is a purely front end change scoped to the deployments table component.
Will you send a PR to implement it?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the global Deployments page (/dashboard/deployments) and locate the deployments table component alongside the existing Status and Type filters. Inspect the deployment.allCentralized query data to derive the available servers, then confirm the table shows only deployments matching the selected server while retaining an All servers default and the Dokploy option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100