Feature Request: Show Deployment Status for Both Frontend and Backend

Aperta
  • Qualcosa non va?
#5,545 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
38.2k
Fork
3.1k
Merge medio
2g 11h
PR unite (30g)
65

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Dokploy/dokploy

Tutte le issue di Dokploy/dokploy

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.