Dynamic Open Graph (OG) Metadata Support #5346

What problem will this feature address?

Currently, when sharing a direct link to a self-hosted Dokploy instance with a team on a messenger or team chat, it only shows a generic, unbranded preview. Dokploy does not render Open Graph tags (og:title, og:description, og:image), resulting in links missing proper context.

This lack of Open Graph metadata is a crucial missing feature for users who are purchasing a license to rebrand Dokploy as their private or internal infrastructure. Even when enterprise whitelabeling features are fully enabled, sharing a link to the dashboard still shows the exact same unbranded Dokploy link preview for everyone, breaking the white-labeling experience.

Describe the solution you'd like

I propose adding dynamic Open Graph metadata support that hooks directly into the existing Enterprise Whitelabeling system.

1. Dynamic Metadata based on License/Whitelabeling:
   • Enterprise users: Use the configured Application Name for og:title and Application Description for og:description.
   • Default/Community: Render fallback placeholders:
     • Title: Dokploy
     • Description: The Open Source alternative to Netlify, Vercel, Heroku.
2. New Whitelabeling Field for og:image:
   • Add a new "OG Image URL" column next to the "Favicon URL" setting under Dashboard > Settings > Whitelabeling.
   • Add a default /og.png image for users who have not set a custom image or who are using the Community version.

The implementation would require updating the JSONB default and Zod schema in @dokploy/server to include a nullable ogImageUrl, adding the frontend UI input, and conditionally rendering the <meta property="og:*"> tags in _document.tsx.

Describe alternatives you've considered

• Relying on the standard <title> tag without OG tags, but modern team messengers (Slack, Discord, Teams) heavily rely on Open Graph for rich link previews. Without it, the links remain unbranded.
• Hardcoding custom OG tags, but this breaks the ease of use of the Dokploy settings UI and doesn't solve it for all users dynamically.

Additional context

Open Questions for Maintainers: @Siumauricio and @narcisonunez

• Deprecating the Page Title field: In /dashboard/settings/whitelabeling, the Page Title field under Metadata & Links feels redundant because users typically want the browser tab title and Open Graph title to simply mirror the Application Name set in the Branding section. Could we adapt the <title> and og:title to just use Application Name directly?
• Renaming the section: If we remove Page Title and rely on Application Name and Application Description for all metadata (including OG), we could rename the Metadata & Links section to simply Links. This keeps all branding (Logo, Favicon, OG Image, Name, Description) consolidated cleanly in the Branding section.

Overall, these changes will make the user experience significantly better and more structured for an enterprise user. It also improves the default link previews for indie devs and small teams using the Community version, providing better marketing visibility for Dokploy itself when they share links.

Will you send a PR to implement it?

Yes. #5348