Make start/stop/status work from anywhere on slave nodes#47
Merged
jonathonbyrdziak merged 1 commit intomasterfrom Mar 20, 2026
Merged
Make start/stop/status work from anywhere on slave nodes#47jonathonbyrdziak merged 1 commit intomasterfrom
jonathonbyrdziak merged 1 commit intomasterfrom
Conversation
Adds NodeConfig::resolveSlaveNode() shared helper that all three commands use to detect slave nodes and resolve the active directory. - protocol start [project]: starts watchers, docker, crontab using NodeConfig to find the active release/branch directory - protocol stop [project]: stops watchers and containers from anywhere - protocol status [project]: already worked, now uses shared resolver - protocol init: automatically runs protocol start at the end of slave node setup (which then runs status for a full dashboard) All three commands accept an optional project name argument for multi-project servers: `protocol start ghostagent` Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
NodeConfig::resolveSlaveNode()— shared helper that detects slave nodes and resolves the active release/branch directoryprotocol start [project]now works from any directory on slave nodes — finds config from~/.protocol/.node/, resolves the active dir, and passes it to all subcommandsprotocol stop [project]— same treatment, stops watchers and containers from anywhereprotocol status [project]— refactored to use the shared resolver (was already working, now consistent)protocol initnow automatically runsprotocol startat the end of slave setup, which in turn runsprotocol status— so after init completes you get the full services started and a status dashboardprojectargument for multi-project servers:protocol start ghostagentTest plan
protocol initon a fresh production node — verify it auto-starts services and shows status at the endprotocol startfrom home directory — verify it finds the slave node and starts watchersprotocol stopfrom home directory — verify it stops watchers and containersprotocol statusfrom home directory — verify full dashboardprotocol start ghostagentwith project name — verify it targets the correct project🤖 Generated with Claude Code