Import/Adopt existing Docker Swarm stacks/services into Dokploy projects for monitoring & management

What problem will this feature address?

I’m running Dokploy on a Swarm manager. I also deploy other stacks/services outside of Dokploy (e.g., via docker stack deploy, Ansible, or other tooling).

Dokploy can “see” these services under the Swarm/Node Applications view (they exist and are running), but they don’t appear under any Dokploy Project/App/Service, so I can’t:

• monitor them in the same place (health/logs/metrics as Dokploy-managed apps)
• manage/restart/scale/roll back from within Dokploy (if those features exist for Dokploy-managed services)
• associate them with a project, env vars, domains, alerts, etc.

This creates a split-brain situation: the cluster is visible, but the workloads are “outside” Dokploy’s project model.

Describe the solution you'd like

Add an “Import / Adopt existing service/stack” workflow that lets me bring existing Swarm resources under Dokploy’s management without recreating them from scratch.

Technical notes / constraints (important)

• Imported services were created externally and may not have Dokploy’s expected labels/metadata.
• Some service attributes may not be reconstructible perfectly from Docker API alone (env files, secrets origin, original compose file, etc.).
• Secrets/networks are often external prerequisites.
• Import should be careful not to break running workloads:
• ideally do not force a redeploy during import unless the user opts in

Describe alternatives you've considered

The only real alternative to what I'm doing, is using Dokploy as the single source of truth and that simply isn't possible for me. I LOVE Dokploy, its a great tool and I hope it will be very successful and many years in my idea...but I can't make Dokploy this hard of a choice. If one day it breaks, I need to be able to function and able to deploy basic things without relying on it. <3

Additional context

Not in particular

Will you send a PR to implement it?

No

Start with the Swarm/Node Applications view and the existing Dokploy Project/App/Service management flow to understand how externally created resources are represented. Define the import/adopt workflow for stacks and services, including missing labels, external secrets and networks, incomplete metadata, and avoiding an automatic redeploy. Done means imported workloads can be associated with a project and managed or monitored without breaking running services.