Feature Request: Deployment History Improvements & Quick Rollback

What problem will this feature address?

Currently, in the deployment section, it is difficult to quickly understand what changed between deployments or identify which deployment should be restored when an issue occurs.

There is limited visibility into:

• The exact Docker Compose version used for each deployment
• Related deployment metadata/configuration
• Easy rollback actions

Describe the solution you'd like

Proposed Solution

Enhance the deployment history view to include:

• Preview of the docker-compose.yml (or compose configuration) used for each deployment
• Deployment metadata such as:
  • Environment variables snapshot
  • Image tags / versions
  • Git commit / branch
  • Deployment timestamp
  • Deployment status and logs shortcut
• Ability to compare deployments
• One-click rollback to a previous deployment/version

Describe alternatives you've considered

• Manually tracking deployment versions through Git commits and tags, but this does not reflect the actual deployed state in Dokploy (e.g., environment changes or overridden compose files).
• Relying on container/image history (Docker images), but this lacks context about the full deployment configuration and associated compose file.
• Maintaining external documentation or changelogs for each deployment, but this becomes error-prone and quickly outdated in fast deployment workflows.
• Rolling back by manually redeploying previous Git commits, which is time-consuming and does not provide a quick “one-click rollback” experience from the UI.

Additional context

Suggested UI Ideas

• Expandable deployment entries
• “View Compose” modal/diff viewer
• “Rollback” button directly in deployment history
• Version badges or labels

Additional Notes

This would make Dokploy deployments much easier to manage in production environments, especially when multiple deployments happen frequently.

Will you send a PR to implement it?

Maybe, need help

Start with the deployment section's history view and trace how each deployment's compose configuration and metadata are recorded. Define the scope with maintainers before work begins; completion would require the agreed history details, comparison view, and rollback flow to be available from the deployment history.