Problem
docker-compose.yml is saturated with the old brand identity across service names, container names, network definitions, and environment variable defaults:
| Element |
Current Value |
| Service name |
unraveldocs-api |
| Container name |
unraveldocs-api |
POSTGRES_DB default |
unraveldocs |
| Postgres healthcheck DB |
unraveldocs |
Elasticsearch cluster.name |
unraveldocs-cluster |
Elasticsearch node.name |
unraveldocs-node |
| Docker network |
unraveldocs-net |
This means docker-compose up starts a container named unraveldocs-api, connects to a database named unraveldocs, and registers an Elasticsearch cluster named unraveldocs-cluster. All three contradict the new brand.
Proposed Solution
Replace all occurrences with xtraction equivalents throughout docker-compose.yml.
User Stories
- As a developer running the local stack, I want Docker container names, network names, and service identifiers to reflect
xtraction so I can easily identify running services.
- As a DevOps engineer, I want Elasticsearch cluster and node names to use the new brand for correct identification in monitoring tools like Kibana and Datadog.
Acceptance Criteria
Proposed Technical Details
# Before
services:
unraveldocs-api:
container_name: unraveldocs-api
...
networks:
unraveldocs-net:
# After
services:
xtraction-api:
container_name: xtraction-api
...
networks:
xtraction-net:
Each service's networks reference must also be updated from unraveldocs-net to xtraction-net.
Tasks
Open Questions / Considerations
- Existing Docker volumes (e.g.,
postgres_data) may contain data from the unraveldocs database. Developers running persistent volumes need to either drop and recreate them or run a database rename. Add a migration note to the PR description.
Problem
docker-compose.ymlis saturated with the old brand identity across service names, container names, network definitions, and environment variable defaults:unraveldocs-apiunraveldocs-apiPOSTGRES_DBdefaultunraveldocsunraveldocscluster.nameunraveldocs-clusternode.nameunraveldocs-nodeunraveldocs-netThis means
docker-compose upstarts a container namedunraveldocs-api, connects to a database namedunraveldocs, and registers an Elasticsearch cluster namedunraveldocs-cluster. All three contradict the new brand.Proposed Solution
Replace all occurrences with
xtractionequivalents throughoutdocker-compose.yml.User Stories
xtractionso I can easily identify running services.Acceptance Criteria
xtraction-apixtraction-apiPOSTGRES_DBdefault isxtractionxtractionDBcluster.name=xtraction-clusternode.name=xtraction-nodextraction-netgrep -i "unraveldocs" docker-compose.ymlreturns zero resultsdocker-compose up -dstarts all services cleanlyProposed Technical Details
Each service's
networksreference must also be updated fromunraveldocs-nettoxtraction-net.Tasks
unraveldocs-api→xtraction-apicontainer_name→xtraction-apiPOSTGRES_DBdefault →xtractioncluster.nameandnode.nameunraveldocs-net→xtraction-netnetworks:references in every service blockdocker-compose up -dand verify all containers startdocker psand confirm container namesOpen Questions / Considerations
postgres_data) may contain data from theunraveldocsdatabase. Developers running persistent volumes need to either drop and recreate them or run a database rename. Add a migration note to the PR description.