Repository navigation
docs(monorepo): clarify that publishing recreates containers with the new image - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
docs/deployment.mdsaid the MCP publish "pulls and restarts" the container. That wording could be read as a restart of the current image. Both the backend and MCP sections now say that the deploy pulls the new image and recreates the container from it, and that--no-depslimits the MCP deploy to its own container.Why
Clarification requested after #15. The behavior is unchanged.
How it was verified
Checked the MCP server 0.5.1 release run (38062320425): the log shows
Image gustmrg/bitfinance-mcp-server:0.5.1 Pulledfollowed byContainer bitfinance-mcp-server RecreatedandStarted.Risks / follow-up
None. Documentation only.