Skip to content

docs: fix vprox command hierarchy to nest under vops#4

Merged
vNodesV merged 1 commit into
mainfrom
vOps_v1.5.5
Jun 19, 2026
Merged

docs: fix vprox command hierarchy to nest under vops#4
vNodesV merged 1 commit into
mainfrom
vOps_v1.5.5

Conversation

@vNodesV

@vNodesV vNodesV commented Jun 19, 2026

Copy link
Copy Markdown
Owner

vProx/vprox was documented as the top-level command in several places (CLI_FLAGS_GUIDE.md, README.md, MODULES.md, INSTALLATION.md, docs/UPGRADE.md) when it's actually a subcommand of vops (vops vprox <start|stop|restart|status|view>). Restructured docs to reflect the correct hierarchy and clearly separated the advanced standalone vProx binary's flag set (only relevant for dev/diagnostics via cmd/vprox directly) from the vops-wrapped service commands.

Summary

Changes

Testing

  • go build ./... passes
  • go vet ./... passes
  • gofmt -w ./... applied
  • Tested manually against a running node (if applicable)

Checklist

  • No secrets or credentials added
  • No speculative refactors — change is minimal and targeted
  • Documentation updated if behavior changed
  • CHANGELOG.md updated (for user-visible changes)

Merge process: All CI checks must pass, then comment /approve to submit review.

vProx/vprox was documented as the top-level command in several places
(CLI_FLAGS_GUIDE.md, README.md, MODULES.md, INSTALLATION.md,
docs/UPGRADE.md) when it's actually a subcommand of vops
(vops vprox <start|stop|restart|status|view>). Restructured docs to
reflect the correct hierarchy and clearly separated the advanced
standalone vProx binary's flag set (only relevant for dev/diagnostics
via cmd/vprox directly) from the vops-wrapped service commands.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vNodesV vNodesV merged commit 9a447b3 into main Jun 19, 2026
5 of 6 checks passed
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