Add “Export as Docker Labels” Feature for Existing Resources

[hilsonp]

Summary

Provide a way in the Pangolin UI to display the equivalent Docker labels for an existing resource configuration.

Motivation

While Docker labels are excellent for configuration-as-code workflows, it is often more convenient to initially create and fine-tune a resource directly in the Pangolin UI. However, once the configuration is validated, users who want to migrate the resource to a label-based setup must manually recreate all fields as Docker labels.
This process is time-consuming, error-prone, and discourages users from adopting label-based configuration, even though it is better aligned with modern Git-driven homelab workflows.

Proposed Solution

Add a feature to the resource details page that displays the full set of Docker labels corresponding to the current configuration. This export could be shown as:
• A dedicated “Show Docker Labels” or “Export as Labels” button.
• A modal or side panel listing all required labels in a ready-to-copy format.
• Correctly formatted labels, including arrays (e.g., targets[0].method), domains, ports, health checks, etc.

This would allow users to:
• Create and test a resource via the UI.
• Export the equivalent labels.
• Paste them directly into their Docker Compose file.
• Delete the UI-based resource and rely fully on labels going forward.

Alternatives Considered

No response

Additional Context

No response

[june012006]

This would help so much. I use git as a source for my docker compose files, so I often have 50+ merges just to get the labels right.

[hilsonp]

Keep in mind that git is your source but not (yet) the source of trust because of this: #1864
Because of this, I refrain to use the labels and will happily use them again when pangolin acts like traefik does with labels.