The previous implementation blindly added HAProxy components without checking for existing configurations on the same port, which caused duplicate entries and errors when a service was updated. This commit refactors the logic to a robust "remove-then-add" strategy. The configure_service method now finds and removes any existing frontend and its dependent components (backend, servers, health check) before adding the new, complete service definition. This change makes the process fully idempotent, preventing configuration drift and ensuring a predictable state. Co-authored-by: Ian Letourneau <letourneau.ian@gmail.com> Reviewed-on: https://git.nationtech.io/NationTech/harmony/pulls/129 |
||
---|---|---|
.cargo | ||
.gitea/workflows | ||
.sqlx | ||
adr | ||
brocade | ||
data | ||
demos/cncf-k8s-quebec-meetup-september-2025 | ||
docs | ||
examples | ||
harmony | ||
harmony_cli | ||
harmony_composer | ||
harmony_inventory_agent | ||
harmony_macros | ||
harmony_secret | ||
harmony_secret_derive | ||
harmony_tui | ||
harmony_types | ||
iobench | ||
k3d | ||
migrations | ||
opnsense-config | ||
opnsense-config-xml | ||
private_repos/example | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
Cargo.lock | ||
Cargo.toml | ||
check.sh | ||
CONTRIBUTING.md | ||
Dockerfile | ||
LICENSE | ||
README.md |
Harmony : Open-source infrastructure orchestration that treats your platform like first-class code
By NationTech
Unify
- Project Scaffolding
- Infrastructure Provisioning
- Application Deployment
- Day-2 operations
All in one strongly-typed Rust codebase.
Deploy anywhere
From a developer laptop to a global production cluster, a single source of truth drives the full software lifecycle.
1 · The Harmony Philosophy
Infrastructure is essential, but it shouldn’t be your core business. Harmony is built on three guiding principles that make modern platforms reliable, repeatable, and easy to reason about.
Principle | What it means for you |
---|---|
Infrastructure as Resilient Code | Replace sprawling YAML and bash scripts with type-safe Rust. Test, refactor, and version your platform just like application code. |
Prove It Works — Before You Deploy | Harmony uses the compiler to verify that your application’s needs match the target environment’s capabilities at compile-time, eliminating an entire class of runtime outages. |
One Unified Model | Software and infrastructure are a single system. Harmony models them together, enabling deep automation—from bare-metal servers to Kubernetes workloads—with zero context switching. |
These principles surface as simple, ergonomic Rust APIs that let teams focus on their product while trusting the platform underneath.
2 · Quick Start
The snippet below spins up a complete production-grade Rust + Leptos Webapp with monitoring. Swap it for your own scores to deploy anything from microservices to machine-learning pipelines.
use harmony::{
inventory::Inventory,
modules::{
application::{
ApplicationScore, RustWebFramework, RustWebapp,
features::{PackagingDeployment, rhob_monitoring::Monitoring},
},
monitoring::alert_channel::discord_alert_channel::DiscordWebhook,
},
topology::K8sAnywhereTopology,
};
use harmony_macros::hurl;
use std::{path::PathBuf, sync::Arc};
#[tokio::main]
async fn main() {
let application = Arc::new(RustWebapp {
name: "harmony-example-leptos".to_string(),
project_root: PathBuf::from(".."), // <== Your project root, usually .. if you use the standard `/harmony` folder
framework: Some(RustWebFramework::Leptos),
service_port: 8080,
});
// Define your Application deployment and the features you want
let app = ApplicationScore {
features: vec![
Box::new(PackagingDeployment {
application: application.clone(),
}),
Box::new(Monitoring {
application: application.clone(),
alert_receiver: vec![
Box::new(DiscordWebhook {
name: "test-discord".to_string(),
url: hurl!("https://discord.doesnt.exist.com"), // <== Get your discord webhook url
}),
],
}),
],
application,
};
harmony_cli::run(
Inventory::autoload(),
K8sAnywhereTopology::from_env(), // <== Deploy to local automatically provisioned local k3d by default or connect to any kubernetes cluster
vec![Box::new(app)],
None,
)
.await
.unwrap();
}
Run it:
cargo run
Harmony analyses the code, shows an execution plan in a TUI, and applies it once you confirm. Same code, same binary—every environment.
3 · Core Concepts
Term | One-liner |
---|---|
Score | Declarative description of the desired state (e.g., LAMPScore ). |
Interpret | Imperative logic that realises a Score on a specific environment. |
Topology | An environment (local k3d, AWS, bare-metal) exposing verified Capabilities (Kubernetes, DNS, …). |
Maestro | Orchestrator that compiles Scores + Topology, ensuring all capabilities line up at compile-time. |
Inventory | Optional catalogue of physical assets for bare-metal and edge deployments. |
A visual overview is in the diagram below.
4 · Install
Prerequisites:
- Rust
- Docker (if you deploy locally)
kubectl
/helm
for Kubernetes-based topologies
git clone https://git.nationtech.io/nationtech/harmony
cd harmony
cargo build --release # builds the CLI, TUI and libraries
5 · Learning More
-
Architectural Decision Records – dive into the rationale
-
Extending Harmony – write new Scores / Interprets, add hardware like OPNsense firewalls, or embed Harmony in your own tooling (
/docs
). -
Community – discussions and roadmap live in GitLab issues. PRs, ideas, and feedback are welcome!
6 · License
Harmony is released under the GNU AGPL v3.
We choose a strong copyleft license to ensure the project—and every improvement to it—remains open and benefits the entire community. Fork it, enhance it, even out-innovate us; just keep it open.
See LICENSE for the full text.
Made with ❤️ & 🦀 by the NationTech and the Harmony community