feat(deployments): filter deployments table by server#4672
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 22c34422f4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const LOCAL_SERVER_VALUE = "__local__"; | ||
|
|
||
| function getServerInfo(d: DeploymentRow) { | ||
| const server = d.server ?? d.application?.server ?? d.compose?.server ?? null; |
There was a problem hiding this comment.
Include build servers in the server filter
When an application deployment uses a separate build server, this helper returns only d.server/application.server/compose.server, while the same table’s Server column also renders d.buildServer/application.buildServer. In that case the dropdown either omits the build server entirely, or selecting that server excludes deployments that visibly list it under “Build:”, so filtering by the server shown in the table gives incomplete results.
Useful? React with 👍 / 👎.
What is this PR about?
This adds a "Server" filter to the global Deployments table (
/dashboard/deployments), making it easy to see what is deployed on a given server when running Dokploy with more than one server.The table already shows a Server column and already supports searching, filtering by status, and filtering by type, but there was no way to scope the list to a single server. This PR adds a Server dropdown next to the existing Status and Type filters. It is populated from the servers present in the current deployments, includes an "All servers" default, and adds a "Dokploy" entry for services that run on the local Dokploy host (no remote server set). The Server column header is already sortable, so together you can group by server and zoom into one.
The change is front end only and scoped to
show-deployments-table.tsx. The server for each deployment is already returned by the existingdeployment.allCentralizedquery, so no API or schema changes were needed.Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
closes #4671
Screenshots (if applicable)
The Deployments toolbar now reads: Search, Status, Type, Server.