Repository navigation
fix(gateway): make standalone MCP deployment boot-safe - #60
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.
The MCP service can fail before Node starts when its sandbox requires temporary bridge and tmux directories that disappeared at boot. Add a standalone systemd installer and generic gateway unit that install persistent tmpfiles rules and prepare those directories with explicit UID, GID and permissions.
The installer plans by default, supports a directories-only mode for host overlays, and never starts or restarts services.
Validation:
npm run verifypassed with an isolatedXDG_STATE_HOME; five deployment tests passed without skips, including real tmpfiles boot recreation, idempotency, permissions, path validation and symlink refusal.