From 92dcb17b8f7de419e2807fde3512316e4f0bd024 Mon Sep 17 00:00:00 2001 From: Gustavo Miranda Date: Sat, 10 Oct 2026 12:17:21 -0300 Subject: [PATCH] docs(monorepo): clarify that publishing recreates containers with the new image --- docs/deployment.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/deployment.md b/docs/deployment.md index a282363..48324a0 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -77,14 +77,16 @@ All publish workflows build from the release tag (`/v`), first che 2. On the server, in `DEPLOY_PATH`, it uses `docker-compose.yml` and `docker-compose.prod.yml` to: - pull the `bitfinance-api` image with `IMAGE_TAG=`; - apply database migrations with `docker compose run --rm --no-deps bitfinance-api --migrate`; - - restart `bitfinance-api` with the new image. + - recreate the `bitfinance-api` container from the new image. The deploy prints the service status and recent logs, including when it fails. ### MCP server 1. Builds `gustmrg/bitfinance-mcp-server` for `linux/amd64` and `linux/arm64` and pushes it to Docker Hub as `` and `latest`. -2. On the server, in `DEPLOY_PATH`, it pulls and restarts only `bitfinance-mcp-server` (`--no-deps`) with `MCP_IMAGE_TAG=`. +2. On the server, in `DEPLOY_PATH`, with `MCP_IMAGE_TAG=`: + - pulls the new `bitfinance-mcp-server` image; + - recreates the `bitfinance-mcp-server` container from it. `--no-deps` leaves the API, database and cache untouched. The backend and the MCP server share the compose project in `apps/backend` (`docker-compose.prod.yml` defines both services) and the same `DEPLOY_PATH`.