feat : Nixopus CLI

[raghavyuva]

Summary by CodeRabbit

• New Features

  • Introduced a comprehensive CLI tool (nixopus) with commands for preflight checks, cloning repositories, configuration management, service management, proxy control, installation, uninstallation, version display, and testing.
  • Added detailed CLI documentation and reference guides.
  • Provided build and install scripts for packaging and deploying the CLI.
  • Implemented advanced configuration management, SSH key handling, and proxy management features.

• Bug Fixes

  • Updated Docker Compose and config files to improve default path handling and service configuration.

• Documentation

  • Added extensive documentation for CLI commands, usage examples, and error handling guidance.
  • Updated project README and navigation to reflect new CLI features.

• Chores

  • Expanded .gitignore to cover Python, macOS, and editor artifacts.
  • Added and updated GitHub Actions workflows for formatting, CLI release, and removed obsolete workflows.

• Tests

  • Added comprehensive unit and integration test suites for all CLI functionalities, including configuration, service, proxy, install, and utility modules.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15933525	Triggered	Generic Password	75089c9	docker-compose-test.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}