Released Torrust Tracker Deployer v0.1.0

Hello, Torrust community!

We're happy to announce the first public release of the Torrust Tracker Deployer: v0.1.0.

This is the milestone that turns the project from an internal effort into a tool you can use today. If you've followed our previous deployer articles, this release includes the workflow we used to deploy the public Torrust Tracker demo in production and all fixes discovered during that real-world validation.

Release Notes Snapshot

This post announces the first stable release. If you want one-screen release-critical information, this section covers support, limitations, upgrade expectations, and how to verify a successful setup.

Compatibility and Scope (v0.1.0)

• Production provider support: Hetzner only
• Container execution: cloud-provider workflows are supported
• LXD support in container mode: not supported

Upgrade and Migration

Since this is the first stable public release (v0.1.0), there is no migration path from a previous stable deployer release yet. Future announcement posts will include explicit upgrade guidance when new stable versions are published.

Known Limitations

• Only Hetzner is supported for production deployments in this version
• Some advanced post-provision operations still require manual steps
• Tracked release-process context is available in issue #462

Quick Verification Checklist

• Confirm CLI help works with the command shown below
• Validate your environment configuration before provisioning
• Run deployment tests after run to confirm service readiness
• Check the demo repository if you need a reference for generated artifacts and operations

What's in v0.1.0

v0.1.0 ships the first complete deployment lifecycle for Torrust Tracker environments. The focus of this release is reliability, reproducibility, and clear operational guidance.

• Production-tested command lifecycle from environment creation to service startup
• Improved validation and error messages from end-to-end deployment testing
• Deployment docs and troubleshooting guidance based on real Hetzner deployments
• Support for running the tool via Docker, reducing local setup complexity

The project remains intentionally opinionated: sensible defaults, a clear sequence of steps, and a single objective - get a tracker deployed correctly with less manual effort.

Another important design choice is architecture: the deployer follows layered Domain-Driven Design (DDD). That approach is uncommon in infrastructure tooling, but it has helped us keep domain logic isolated from provider/tool integrations and made the system easier to evolve and test as it grew.

Why this release matters

Historically, deploying Torrust Tracker in production required many manual tasks across server provisioning, networking, TLS, container configuration, and service checks. With the deployer, those operations are organized into a reproducible workflow with structured state and tests.

In our latest deployment report, we used the deployer to bring the public demo online and fixed 11 issues discovered during the process. Those fixes are part of the path to this v0.1.0 release.

Built Entirely With AI Agents

As mentioned in our previous deployer article, the Torrust Tracker Deployer was built entirely using AI agents. We started this effort at the end of September 2025 and continued iterating through architecture, implementation, testing, and documentation.

To give an idea of the scope, here are the latest code statistics from the automated code-statistics workflow:

• 1,844 files tracked in the repository
• 344,370 total lines (code + comments + blanks)
• 175,769 code lines across all languages
• 107,124 comment lines for documentation and explanations
• 61,477 blank lines for structure and readability
• 804 Rust files with 85,323 Rust code lines
• 438 Markdown files with 84,184 Markdown lines

Quick start overview

The deployer workflow is sequential. At a high level, you'll create a config template, validate it, create the environment, provision infrastructure, configure and release artifacts, run services, and then test the deployment.

If you want to see the CLI help, you can run:

docker run --rm torrust/tracker-deployer:latest --help

For a complete tutorial with practical examples and provider-specific notes, read: Deploying the Torrust Tracker Demo with the Torrust Tracker Deployer.

You can also inspect the final generated configuration and deployment artifacts in the Torrust Tracker Demo repository. It is useful for learning the extra maintenance and operational tasks that happen after the initial deployment.

What's next

We'll continue improving automation coverage, provider integrations, and deployment ergonomics. As adoption grows, we'll prioritize issues reported by users running real environments.

• Better support for production patterns that still need manual intervention
• Expanded provider and deployment scenario documentation
• Iterative UX improvements in commands, validation, and recovery guidance

How you can help

If you run a tracker, test infrastructure workflows, or simply want to help improve deployment tooling in the BitTorrent ecosystem, your feedback is extremely valuable.

• Try v0.1.0 in your own environment and share your experience by opening an issue
• Report bugs or unclear documentation in issues
• Contribute improvements in code, docs, or tests via pull requests

Thanks to everyone who tested early versions and helped shape this first release. Onward to the next iteration.