feat(env): added COOLIFY_RESOURCE_UUID environment variable

[nktnet1]

Changes

• injects the COOLIFY_RESOURCE_UUID environment variable

Issues

• relates to [Improvement]: Add a container name environment variable/ a uuid environment variable #2545

---

Use Case

When a docker compose stack has the following:

1. uses redis
2. have Connect to Predefined Networks enabled
3. has a file mount config (e.g. superset_config.py) which needs to reference the redis service

Because of (2), the docker compose's redis service will be overshadowed by Coolify's redis when referenced in (3), the file mount config.

The workaround is as described in my #4891 (comment) - basically, in the file mount config, extract the UUID such as:

# superset_config.py
 
COOLIFY_UUID = os.getenv('COOLIFY_CONTAINER_NAME').strip('"').split('-')[-1]

Then use this to reference the correct redis (and postgres) containers, e.g.

# use redis-{COOLIFY_UUID}
CACHE_REDIS_URL =  f"redis://:{os.getenv('REDIS_PASSWORD')}@redis-{COOLIFY_UUID}:6379/1"

# use db-{COOLIFY_UUID}
SQLALCHEMY_DATABASE_URI = f"postgresql+psycopg2://{os.getenv('POSTGRES_USER')}:{os.getenv('POSTGRES_PASSWORD')}@db-{COOLIFY_UUID}:5432/{os.getenv('POSTGRES_DB')}"

This pull request simplifies this process by providing the UUID directly as an environment variable, rather than requiring manual parsing from COOLIFY_CONTAINER_NAME to extract this value.

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: bootstrap/helpers/shared.php

Function	Unhandled Issue
parseDockerComposeFile	Exception: Unable to parse at line 1 (near " n8n:"). livewire?component=project.service.n... Event Count: 1

---

_{Did you find this useful? React with a 👍 or 👎}

[andrasbacsai]

Thank you for the PR! It makes sense.

[nktnet1]

Thank you @andrasbacsai!

I've made a corresponding PR for documentation-coolify here:

• feat(env): documented COOLIFY_RESOURCE_UUID documentation-coolify#153