Skip to content

Conversation

@albertorizzi
Copy link
Contributor

@albertorizzi albertorizzi commented Jan 7, 2026

Motivation

When monitoring containers through tools like Dozzle, users see container names and IDs (e.g., s4o8kw8ggk4g4go44gsg84kg-101632532767 or s4o8kw8ggk4g4go44gsg84kg:fe2cb64017b313fdb2523a5431b5caa2a3033d4e) but have no easy way to map them back to their corresponding resources in Coolify. This PR addresses this by making container identifiers (UUIDs) searchable in the global search, enabling users to quickly find the associated application, service, or database.

Summary

  • Add UUID to search terms for applications, services, and databases
  • Add PR search terms for applications with preview enabled
  • Include service component names (applications and databases) in search
  • Add eager loading for previews and databases relationships

Changes

  • Enhanced search terms for applications: Added UUID and PR (pull request) search terms to application search. Users can now search for applications by their container UUID or by PR numbers (e.g., "pr-123", "pr123", or just "123") when preview is enabled. This allows users to paste a container name from Docker/Dozzle and immediately find the corresponding application in Coolify.

  • Enhanced search terms for services: Added UUID and component names (applications and databases) to service search terms. Since service containers use the pattern {name}-{service.uuid}, users can now search by either the service UUID or individual component names to quickly locate the service.

  • Enhanced search terms for databases: Added UUID to search terms for all database types (PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, ClickHouse). Users can search databases by their container UUID, making it easy to identify which database a container belongs to.

  • Performance optimization: Added eager loading for previews relationship in applications and databases relationship in services to prevent N+1 query issues while maintaining the existing 5-minute cache strategy.

Use Cases

  1. From Dozzle to Coolify: User sees container s4o8kw8ggk4g4go44gsg84kg-101632532767 in Dozzle → searches for s4o8kw8ggk4g4go44gsg84kg in Coolify → immediately finds the application
  2. PR Container Debugging: User sees a container with -pr-42 in the name → searches for pr-42 or just 42 → finds all PR preview containers
  3. Service Component Lookup: User sees postgres-abc123def container → searches for the UUID or "postgres" → finds the service

Issues

  • N/A

albertorizzi and others added 2 commits January 7, 2026 16:33
- Add UUID to search terms for applications, services, and databases
- Add PR search terms for applications with preview enabled
- Include service component names (applications and databases) in search
- Add eager loading for previews and databases relationships
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant