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. +
+ ++ 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. +
+ +
+ 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.
+
run to confirm service readiness+ 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. +
+ ++ 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. +
+ ++ 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. +
+ ++ 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: +
+ ++ 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:
+ ++ 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. +
+ ++ We'll continue improving automation coverage, provider integrations, and deployment + ergonomics. As adoption grows, we'll prioritize issues reported by users running real + environments. +
+ ++ 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. +
+ ++ Thanks to everyone who tested early versions and helped shape this first release. Onward + to the next iteration. +
+