Feature Request: Show Deployment Status for Both Frontend and Backend

Open
  • Is something wrong?
#5,545 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
devops

Research direction

No file, test, or entry point is named in the issue. Start by tracing how deployment state is displayed for frontend and backend environments, then verify that a triggered deployment shows Pending until it starts, changes to Running when active, and remains visible for both environments.

Written by the indexing model from the issue text.

Description

enhancement
What problem will this feature address?

When deploying both frontend and backend services, the deployment status is only displayed on the environment where the deployment is actively running. The other environment shows no status, making it unclear whether its deployment was triggered, is waiting, or failed to start. A Pending status would provide clear visibility into the deployment state and prevent confusion.

Describe the solution you'd like

Show a Pending deployment status for any environment where a deployment has been triggered but has not started yet. For example, if the frontend deployment is currently running and the backend deployment is waiting, the frontend should show Running and the backend should show Pending. Once the backend deployment starts, its status should automatically change to Running.

Describe alternatives you've considered

We considered continuing with the current behavior where only the actively running deployment displays a status. However, this does not provide enough visibility into deployments that have been triggered but are still waiting to start. Another option would be to display a generic deployment notification, but showing a clear Pending status directly on the affected environment would provide better visibility and reduce confusion.

Additional context

This scenario commonly occurs when frontend and backend services are deployed together and both branch changes are triggered around the same time. Currently, only one environment shows the deployment status, while the other appears to have no active deployment information. Showing the deployment state for each environment, including Running and Pending, would make the deployment process easier to understand and provide users with better visibility into the status of each service.

Will you send a PR to implement it?

No

Dominant language
TypeScript
Stars
38.2k
Forks
3.1k
Avg merge
2d 11m
Merged PRs (30d)
66

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Dokploy/dokploy

All issues in Dokploy/dokploy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.