Skip to content

chore(backend): name the compose project like production - #19

Merged
gustmrg merged 1 commit into
mainfrom
chore/align-compose-project-name
Oct 11, 2026
Merged

gustmrg merged 1 commit into
mainfrom
chore/align-compose-project-name

Conversation

@gustmrg

@gustmrg gustmrg commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • docker-compose.yml: project name bitfinance-backend → bitfinance, the name production already runs under. Copying the repo files to the server no longer creates a second project that clashes with the running containers.
  • docker-compose.prod.yml: container_name: bitfinance-mcp-server, matching the running container and the other services.
  • README: local volumes are now prefixed bitfinance_.

Local dev: existing bitfinance-backend_* volumes are no longer used; the stack starts with fresh volumes.

Rollout

The server's compose files are replaced with these by hand; the rendered config is diffed and up --dry-run checked so only bitfinance-api is recreated (its port becomes 127.0.0.1:8080, which nginx already uses).

Use the bitfinance project name the production server already runs
under and pin the MCP server container name, so the repository compose
files can be copied to the server without recreating the stack.
@gustmrg
gustmrg merged commit 943b36f into main Oct 11, 2026
4 checks passed
@gustmrg
gustmrg deleted the chore/align-compose-project-name branch October 11, 2026 15:33
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