تشغيل أي مهارة في Manus بنقرة واحدة

install-system-dependencies

النجوم٤

التفرعات٢

آخر تحديث١٤ أبريل ٢٠٢٦ في ١٥:٣٩

Install the system dependencies required by the deployer (OpenTofu, Ansible, LXD, cargo-machete) using the built-in dependency-installer. This is the setup/installer step before using the deployer for the first time. Triggers on "install dependencies", "install system dependencies", "setup deployer", "first time setup", "missing dependency", "install opentofu", "install ansible", "install lxd", or "deployer setup".

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

torrust

torrust/torrust-tracker-deployer

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مديرو الشبكات وأنظمة الحاسوبمهن الحاسوب والرياضيات·SOC 15-1244

SKILL.md

readonly

name	install-system-dependencies
description	Install the system dependencies required by the deployer (OpenTofu, Ansible, LXD, cargo-machete) using the built-in dependency-installer. This is the setup/installer step before using the deployer for the first time. Triggers on "install dependencies", "install system dependencies", "setup deployer", "first time setup", "missing dependency", "install opentofu", "install ansible", "install lxd", or "deployer setup".
metadata	{"author":"torrust","version":"1.0"}

Install System Dependencies

Use the built-in dependency-installer package to install all tools required to run the deployer.

Recommended Setup Workflow

# 1. Check what is already installed
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer check

# 2. Install everything missing in one command
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install

# 3. Verify all dependencies are now present
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer check

Commands

# Install all missing dependencies
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install

# Install a specific dependency
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install --dependency opentofu

# Install with verbose output (shows download/install steps)
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install --verbose

Dependencies Installed

Dependency	Purpose
`opentofu`	Infrastructure provisioning (`provision`)
`ansible`	VM configuration (`configure`, `release`)
`lxd`	Local VM provider (LXD environments)
`cargo-machete`	Unused dependency detection (linter / CI)

Exit Codes

0 — All dependencies installed successfully
1 — One or more installations failed
2 — Invalid arguments
3 — Internal error

Notes

The install subcommand requires system package manager access (may prompt for sudo)
Internet access is required to download installers (OpenTofu fetches from opentofu.org)
After installation, re-run check to confirm everything is ready
In GitHub Copilot agent environments, outbound network access to opentofu.org must be allowlisted — see docs/contributing/copilot-agent/firewall.md

المزيد من هذا المستودع

نفس المستودع

release-new-version

torrust/torrust-tracker-deployer

Guide for releasing a new version of the deployer using the standard branch/tag workflow. Covers version bump, signed release commit, pushing main, creating signed tag, creating release branch, and verifying Docker + crate publication workflows. Use when asked to "release", "cut a version", "publish a new version", or "create release vX.Y.Z".

2026-04-144

run-local-e2e-test

torrust/torrust-tracker-deployer

Run a complete local end-to-end test using the LXD provider to verify a feature, fix, or change works as expected from the user's perspective. Covers creating an environment config, provisioning a VM, deploying the tracker, verifying it works, and cleaning up. Use when manually testing changes, validating a new feature locally, running a full deployment smoke test, or checking that the deployer works end-to-end. Triggers on "local e2e", "manual e2e test", "test my changes locally", "run deployer end-to-end", "smoke test", "test on LXD", "verify feature works", or "full deployment test".

2026-04-144

check-system-dependencies

torrust/torrust-tracker-deployer

Check whether the system has all dependencies required by the deployer (OpenTofu, Ansible, LXD, cargo-machete). Use before running provisioning, E2E tests, or any infrastructure command. Triggers on "check dependencies", "check system dependencies", "are dependencies installed", "verify dependencies", "dependency check", or "missing tools".

2026-04-144

open-pull-request

torrust/torrust-tracker-deployer

Open a pull request from a feature branch using GitHub CLI (preferred) or GitHub MCP tools. Covers pre-flight checks, correct base/head configuration for fork workflows, title/body conventions, and post-creation validation. Use when asked to "open PR", "create pull request", or "submit branch for review".

2026-04-144

update-dependencies

torrust/torrust-tracker-deployer

Guide for updating project dependencies using the update-dependencies.sh automation script. Automates the cargo update workflow including branch creation, commit, push, and optional PR creation. Use when updating dependencies, running cargo update, or automating the dependency lifecycle. Triggers on "update dependencies", "cargo update", "update deps", "bump dependencies", or "run dependency update".

2026-04-134

commit-changes

torrust/torrust-tracker-deployer

Guide for committing changes in the torrust-tracker-deployer project. Covers conventional commit format, pre-commit verification checks, issue number conventions, and commit quality guidelines. Use when committing code, running pre-commit checks, or following project commit standards. Triggers on "commit", "commit changes", "how to commit", "pre-commit", "commit message", "commit format", or "conventional commits".

2026-04-134

name	install-system-dependencies
description	Install the system dependencies required by the deployer (OpenTofu, Ansible, LXD, cargo-machete) using the built-in dependency-installer. This is the setup/installer step before using the deployer for the first time. Triggers on "install dependencies", "install system dependencies", "setup deployer", "first time setup", "missing dependency", "install opentofu", "install ansible", "install lxd", or "deployer setup".
metadata	{"author":"torrust","version":"1.0"}

Install System Dependencies

Use the built-in dependency-installer package to install all tools required to run the deployer.

Recommended Setup Workflow

# 1. Check what is already installed
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer check

# 2. Install everything missing in one command
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install

# 3. Verify all dependencies are now present
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer check

Commands

# Install all missing dependencies
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install

# Install a specific dependency
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install --dependency opentofu

# Install with verbose output (shows download/install steps)
cargo run -p torrust-tracker-deployer-dependency-installer --bin dependency-installer install --verbose

Dependencies Installed

Dependency	Purpose
`opentofu`	Infrastructure provisioning (`provision`)
`ansible`	VM configuration (`configure`, `release`)
`lxd`	Local VM provider (LXD environments)
`cargo-machete`	Unused dependency detection (linter / CI)

Exit Codes

0 — All dependencies installed successfully
1 — One or more installations failed
2 — Invalid arguments
3 — Internal error

Notes

The install subcommand requires system package manager access (may prompt for sudo)
Internet access is required to download installers (OpenTofu fetches from opentofu.org)
After installation, re-run check to confirm everything is ready
In GitHub Copilot agent environments, outbound network access to opentofu.org must be allowlisted — see docs/contributing/copilot-agent/firewall.md