Barn Blog
Engineering updates, architectural essays, and release records for Barn. For step-by-step usage guides and command references, see the Documentation.
- Release Notes — Version highlights, upgrade instructions, and dated validation records. Current release: Barn 1.1.0.
- Design Notes — Architectural decisions behind Barn’s single-deployment model, Ansible inventory compatibility, in-place convergence, and host networking.
Barn 1.2.0 release readiness and acceptance
Release gates, upgrade compatibility, packaging, and physical-host acceptance for Barn 1.2.0.
Barn 1.2.0: resources, root growth, and host names
Resource overrides, recoverable root-disk growth, configurable concurrency, inventory host names, and Go 1.27.4.
In-place root growth: recovery and native acceptance
The grow-only resize -D contract, offline and guest expansion, failure recovery, and ext4/XFS native acceptance.
VM specification parameters: commands, short flags, environment, and root disks
A unified CLI, environment, inventory precedence, command scope, and persistence contract for image, architecture, CPU, memory, scale, and root disk size.
Pigsty host setup: fixed names and CA trust
A small, explicit macOS and Linux setup operation for stable Pigsty portal names and the lab's root CA.
Main and command reference review
Git state, version boundaries, command coverage, and validation evidence from the 2026-11-11 Barn review.
Host DNS and domain resolution for Pigsty on Barn
An explicit hosts workflow, Pigsty-owned name semantics, source replacement safeguards, and an optional split-DNS upgrade path for macOS and Linux.
Replacing Vagrant with Barn in Pigsty: resources, names, and migration work
An audit of Pigsty's Vagrant workflow, the vm_scale and local hosts contracts, and an ordered migration plan based on 54 inventory templates.
Barn 1.1.0: image selection and live progress
Select Linux images and guest architectures from the CLI, follow live progress, and recover interrupted resource resizing.
Beyond amd64 and arm64
How guest architecture selects an emulator, machine, firmware, devices, and acceptance tests in Barn.
Running Barn from Windows
Why a Linux host remains necessary, what WSL2 must prove, and what a native Windows backend would require.
What Barn Can Learn from Vagrant
A proposal for repeatable provisioning, environment records, file transfer, and recovery in Pigsty labs.
From Upstream Images to a Signed Catalog
How Barn separates upstream release metadata, catalog evidence, runtime support, and release acceptance.
Barn 1.0.0: the first stable release
Barn's first stable release hardens destructive operations, data-disk recovery, catalog integrity, and cancellation, and updates image catalog revision to 2026110502.
Evolving the CLI Without Breaking Its Contracts
What to preserve when separating Barn's command tree, application orchestration, and output handling.
Barn 0.9.3: safer resizing, selected nodes, and recovery
Resource-only VM resize, independent node selection, flexible paths and shares, recoverable lifecycle operations, and image catalog revision 2026102802.
Barn 0.9.2: signed Barn.app and explicit SSH/exec arguments
Signed and notarized Barn.app in the Apple Silicon release and Homebrew installation, plus the SSH/exec argument contract.
Barn 0.9.1: Go 1.27.3 toolchain and Barn.app rename
Go 1.27.3, current dependencies, and Barn.app naming and signing. Upgrade notes.
Barn 0.9.0: native macOS guests and smoother Linux recovery
Linux labs, native macOS machines, clearer diagnostics, and recovery for interrupted operations.
The Lifetime of a Native Mac VM
Why Barn uses named Mac machines, process-owned networks, narrow locks, and explicit recovery evidence.
Barn 0.8.0: clearer recovery and refreshed images
Recover host preparation, isolate failed nodes, preserve VM identities, and start the September Debian and Ubuntu images.
Barn 0.7.0: simpler test labs and automatic recovery
A shorter first run, compact progress, independent guest setup, and recovery through up.
Barn 0.6.0: Ubuntu 24.04 and smoother local labs
Ubuntu 24.04 defaults, useful plans before setup, clearer status, and reliable expansion and recreation.
Barn 0.5.0: explicit disposal, explicit repositories, reproducible images
A no-confirmation whole-lab purge, explicit global and China repository selection, no hidden artifact fallback, and an eight-target official-image candidate pipeline.
Barn 0.4.0: one command, working data disks, one voice
A first run that is one command, a default data disk that works on every image, readiness failures that name the cause, and one output style across the CLI.
Barn 0.3.0: explicit catalogs and actionable readiness
Explicit image-catalog updates, per-node bootstrap diagnostics, native guest interface names, and a smaller CLI.
Barn 0.2.0: selected convergence and release integrity
VPN-aware network preflight, truly selected scale-out, committed-state integrations, checksum-verified multi-platform artifacts, and the 0.1.0 upgrade boundary.
repo.yaml Is Intent; catalog.json Is Evidence
Why Barn separates human-authored image policy from generated metadata that must match the actual qcow2 artifacts.
A PID Is Not a Virtual Machine
Why Barn combines QMP identity, process evidence, typed invocations, and journals before it signals or deletes anything.
Declarative Does Not Mean Destructive
How Barn uses per-node hashes and explicit operations so missing configuration can never authorize deletion.
Why Every Barn Node Has Two NICs
Why Barn separates management egress from the fixed-address network used by the host, peers, Ansible, and Pigsty.
Why Barn Has No Projects
Why Barn replaced per-directory project state with one owner-scoped deployment driven by one Pigsty inventory.
RC6 development candidate: owner-scoped Tier-1 delivery
Exact RC6 identity, four requested native product passes, durable network transactions, reproducible local archives, and the boundary that keeps this candidate unpublished.
Development snapshot: the Go 1.27 product surface
Quick and four-node private semantics, schema-3 owned profiles, Pigsty inventory integration, persistence, state migration, and verified release mechanisms.
Barn 1.2.0 release readiness and acceptance
Release gates, upgrade compatibility, packaging, and physical-host acceptance for Barn 1.2.0.
Barn 1.2.0: resources, root growth, and host names
Resource overrides, recoverable root-disk growth, configurable concurrency, inventory host names, and Go 1.27.4.
In-place root growth: recovery and native acceptance
The grow-only resize -D contract, offline and guest expansion, failure recovery, and ext4/XFS native acceptance.
VM specification parameters: commands, short flags, environment, and root disks
A unified CLI, environment, inventory precedence, command scope, and persistence contract for image, architecture, CPU, memory, scale, and root disk size.
Pigsty host setup: fixed names and CA trust
A small, explicit macOS and Linux setup operation for stable Pigsty portal names and the lab's root CA.
Main and command reference review
Git state, version boundaries, command coverage, and validation evidence from the 2026-11-11 Barn review.
Host DNS and domain resolution for Pigsty on Barn
An explicit hosts workflow, Pigsty-owned name semantics, source replacement safeguards, and an optional split-DNS upgrade path for macOS and Linux.
Replacing Vagrant with Barn in Pigsty: resources, names, and migration work
An audit of Pigsty's Vagrant workflow, the vm_scale and local hosts contracts, and an ordered migration plan based on 54 inventory templates.
Barn 1.1.0: image selection and live progress
Select Linux images and guest architectures from the CLI, follow live progress, and recover interrupted resource resizing.
Beyond amd64 and arm64
How guest architecture selects an emulator, machine, firmware, devices, and acceptance tests in Barn.
Running Barn from Windows
Why a Linux host remains necessary, what WSL2 must prove, and what a native Windows backend would require.
What Barn Can Learn from Vagrant
A proposal for repeatable provisioning, environment records, file transfer, and recovery in Pigsty labs.
From Upstream Images to a Signed Catalog
How Barn separates upstream release metadata, catalog evidence, runtime support, and release acceptance.
Barn 1.0.0: the first stable release
Barn's first stable release hardens destructive operations, data-disk recovery, catalog integrity, and cancellation, and updates image catalog revision to 2026110502.
Evolving the CLI Without Breaking Its Contracts
What to preserve when separating Barn's command tree, application orchestration, and output handling.
Barn 0.9.3: safer resizing, selected nodes, and recovery
Resource-only VM resize, independent node selection, flexible paths and shares, recoverable lifecycle operations, and image catalog revision 2026102802.
Barn 0.9.2: signed Barn.app and explicit SSH/exec arguments
Signed and notarized Barn.app in the Apple Silicon release and Homebrew installation, plus the SSH/exec argument contract.
Barn 0.9.1: Go 1.27.3 toolchain and Barn.app rename
Go 1.27.3, current dependencies, and Barn.app naming and signing. Upgrade notes.
Barn 0.9.0: native macOS guests and smoother Linux recovery
Linux labs, native macOS machines, clearer diagnostics, and recovery for interrupted operations.
The Lifetime of a Native Mac VM
Why Barn uses named Mac machines, process-owned networks, narrow locks, and explicit recovery evidence.
Barn 0.8.0: clearer recovery and refreshed images
Recover host preparation, isolate failed nodes, preserve VM identities, and start the September Debian and Ubuntu images.
Barn 0.7.0: simpler test labs and automatic recovery
A shorter first run, compact progress, independent guest setup, and recovery through up.
Barn 0.6.0: Ubuntu 24.04 and smoother local labs
Ubuntu 24.04 defaults, useful plans before setup, clearer status, and reliable expansion and recreation.
Barn 0.5.0: explicit disposal, explicit repositories, reproducible images
A no-confirmation whole-lab purge, explicit global and China repository selection, no hidden artifact fallback, and an eight-target official-image candidate pipeline.
Barn 0.4.0: one command, working data disks, one voice
A first run that is one command, a default data disk that works on every image, readiness failures that name the cause, and one output style across the CLI.
Barn 0.3.0: explicit catalogs and actionable readiness
Explicit image-catalog updates, per-node bootstrap diagnostics, native guest interface names, and a smaller CLI.
Barn 0.2.0: selected convergence and release integrity
VPN-aware network preflight, truly selected scale-out, committed-state integrations, checksum-verified multi-platform artifacts, and the 0.1.0 upgrade boundary.
repo.yaml Is Intent; catalog.json Is Evidence
Why Barn separates human-authored image policy from generated metadata that must match the actual qcow2 artifacts.
A PID Is Not a Virtual Machine
Why Barn combines QMP identity, process evidence, typed invocations, and journals before it signals or deletes anything.
Declarative Does Not Mean Destructive
How Barn uses per-node hashes and explicit operations so missing configuration can never authorize deletion.
Why Every Barn Node Has Two NICs
Why Barn separates management egress from the fixed-address network used by the host, peers, Ansible, and Pigsty.
Why Barn Has No Projects
Why Barn replaced per-directory project state with one owner-scoped deployment driven by one Pigsty inventory.
RC6 development candidate: owner-scoped Tier-1 delivery
Exact RC6 identity, four requested native product passes, durable network transactions, reproducible local archives, and the boundary that keeps this candidate unpublished.
Development snapshot: the Go 1.27 product surface
Quick and four-node private semantics, schema-3 owned profiles, Pigsty inventory integration, persistence, state migration, and verified release mechanisms.
-
Barn 1.2.0 release readiness and acceptance
Status, 2026-11-12: Barn 1.2.0 is published as stable/latest. Its final acceptance is recorded below; the candidate sections preserve the earlier review and its original scope. Final release Tag v1.2.0 points to …
Status, 2026-11-12: Barn 1.2.0 is published as stable/latest. Its final acceptance is recorded below; the candidate sections preserve the earlier review and its original scope. Final release Tag v1.2.0 points to …
-
Barn 1.2.0: resources, root growth, and host names
Barn 1.2.0 was released on 2026-11-12 from commit 90f6158. It adds resource overrides, recoverable root-disk growth, configurable lifecycle concurrency, and inventory-based host names. The bilingual command reference covers all 57 operation commands …
Barn 1.2.0 was released on 2026-11-12 from commit 90f6158. It adds resource overrides, recoverable root-disk growth, configurable lifecycle concurrency, and inventory-based host names. The bilingual command reference covers all 57 operation commands …
-
In-place root growth: recovery and native acceptance
Status (2026-11-11): The unreleased development build implements barn resize -D, with ext4 and XFS acceptance on macOS/arm64 using QEMU/HVF guests. Released 1.1.0 still limits resize to CPU/memory. See VM specification design for input precedence and …
Status (2026-11-11): The unreleased development build implements barn resize -D, with ext4 and XFS acceptance on macOS/arm64 using QEMU/HVF guests. Released 1.1.0 still limits resize to CPU/memory. See VM specification design for input precedence and …
-
VM specification parameters: commands, short flags, environment, and root disks
Image, architecture, CPU, memory, scale, and root disk size form one set of VM specification inputs, with consistent names, value rules, and source tracking. Each command declares which fields it accepts and which changes it can apply; the resolution …
Image, architecture, CPU, memory, scale, and root disk size form one set of VM specification inputs, with consistent names, value rules, and source tracking. Each command declares which fields it accepts and which changes it can apply; the resolution …
-
Pigsty host setup: fixed names and CA trust
Recommend one optional host setup operation: install a fixed set of Pigsty names and trust the lab’s public root CA certificate. Keep one entry address, defaulting to 10.10.10.10, and reuse the same CA across ordinary lab rebuilds. With unchanged …
Recommend one optional host setup operation: install a fixed set of Pigsty names and trust the lab’s public root CA certificate. Keep one entry address, defaulting to 10.10.10.10, and reuse the same CA across ordinary lab rebuilds. With unchanged …
-
Main and command reference review
Reviewed on 2026-11-11. Both repositories were on main, but neither had a clean working tree or matched its fetched remote head. The source checks passed on the reviewed working tree. The documentation now has a complete command reference with …
Reviewed on 2026-11-11. Both repositories were on main, but neither had a clean working tree or matched its fetched remote head. The source checks passed on the reviewed working tree. The documentation now has a complete command reference with …
-
Host DNS and domain resolution for Pigsty on Barn
Note Scope narrowed on 2026-11-11: the first delivery is now fixed core names and Pigsty CA trust. This page retains the broader exporter and resolver research; its general inventory and split-DNS work is optional expansion, not a prerequisite for …
Note Scope narrowed on 2026-11-11: the first delivery is now fixed core names and Pigsty CA trust. This page retains the broader exporter and resolver research; its general inventory and split-DNS work is optional expansion, not a prerequisite for …
-
Replacing Vagrant with Barn in Pigsty: resources, names, and migration work
Pigsty can use one inventory for Barn and Ansible. The migration needs to preserve topology selection, image matrices, resource scaling, fixed addresses, and SSH workflows while replacing the old scripts’ implicit addressing, naming, and destruction …
Pigsty can use one inventory for Barn and Ansible. The migration needs to preserve topology selection, image matrices, resource scaling, fixed addresses, and SSH workflows while replacing the old scripts’ implicit addressing, naming, and destruction …
-
Barn 1.1.0: image selection and live progress
Released on 2026-11-09. Barn 1.1.0 adds image and guest-architecture overrides, live progress tables, and more reliable CPU/memory resizing. It embeds signed image catalog revision 2026110502, with 9 distribution releases and 17 architecture-specific …
Released on 2026-11-09. Barn 1.1.0 adds image and guest-architecture overrides, live progress tables, and more reliable CPU/memory resizing. It embeds signed image catalog revision 2026110502, with 9 distribution releases and 17 architecture-specific …
-
Beyond amd64 and arm64
Barn currently supports amd64 and arm64 Linux guests. QEMU can emulate more architectures, but each additional Barn target needs an image and a complete boot-and-operation contract. This design assessment, reviewed on 2026-11-08, separates the …
Barn currently supports amd64 and arm64 Linux guests. QEMU can emulate more architectures, but each additional Barn target needs an image and a complete boot-and-operation contract. This design assessment, reviewed on 2026-11-08, separates the …
-
Running Barn from Windows
Barn’s current host profiles and release binaries cover macOS and Linux on amd64 and arm64. There is no native Windows Barn release. A Windows user can operate Barn through a Linux host; WSL2 and a nested Linux VM are candidates for bringing that …
Barn’s current host profiles and release binaries cover macOS and Linux on amd64 and arm64. There is no native Windows Barn release. A Windows user can operate Barn through a Linux host; WSL2 and a nested Linux VM are candidates for bringing that …
-
What Barn Can Learn from Vagrant
Barn already creates multi-node Linux labs from Pigsty-compatible inventories, manages their lifecycle, and exposes SSH and structured output. The useful lessons from Vagrant concern what happens between creating a VM and repeating an experiment: run …
Barn already creates multi-node Linux labs from Pigsty-compatible inventories, manages their lifecycle, and exposes SSH and structured output. The useful lessons from Vagrant concern what happens between creating a VM and repeating an experiment: run …
-
From Upstream Images to a Signed Catalog
An image audit answers a narrower question than an image release. It can find a newer upstream file, but Barn may add that file to its signed catalog only after the artifact, runtime profile, and boot path have all been verified. The image reference …
An image audit answers a narrower question than an image release. It can find a newer upstream file, but Barn may add that file to its signed catalog only after the artifact, runtime profile, and boot path have all been verified. The image reference …
-
Barn 1.0.0: the first stable release
Released on 2026-11-05. Barn 1.0.0 is the first stable release. For the latest stable release, see Barn 1.1.0. Barn 1.0.0 completes a pre-release audit of destructive operations, data-disk recovery, catalog integrity, and process cancellation. It …
Released on 2026-11-05. Barn 1.0.0 is the first stable release. For the latest stable release, see Barn 1.1.0. Barn 1.0.0 completes a pre-release audit of destructive operations, data-disk recovery, catalog integrity, and process cancellation. It …
-
Evolving the CLI Without Breaking Its Contracts
Barn already uses Cobra. The useful part of the 2026-11-04 CLI proposal is its separation of command syntax, application orchestration, and observable behavior. This essay retains that design, checked against v1.1.0 on 2026-11-09. The package split …
Barn already uses Cobra. The useful part of the 2026-11-04 CLI proposal is its separation of command syntax, application orchestration, and observable behavior. This essay retains that design, checked against v1.1.0 on 2026-11-09. The package split …
-
Barn 0.9.3: safer resizing, selected nodes, and recovery
Released on 2026-10-31. Barn 0.x releases use GitHub’s pre-release channel. For the latest release, see Barn 1.1.0. Barn 0.9.3 focuses on safer changes to local labs. It adds resource-only VM resize, lets selected nodes converge independently, …
Released on 2026-10-31. Barn 0.x releases use GitHub’s pre-release channel. For the latest release, see Barn 1.1.0. Barn 0.9.3 focuses on safer changes to local labs. It adds resource-only VM resize, lets selected nodes converge independently, …
-
Barn 0.9.2: signed Barn.app and explicit SSH/exec arguments
Released on 2026-10-30. Barn 0.x releases use GitHub’s pre-release channel. Barn 0.9.2 includes the complete native macOS guest runtime in the Apple Silicon download and Homebrew installation. You can create Linux and macOS VMs after installing a …
Released on 2026-10-30. Barn 0.x releases use GitHub’s pre-release channel. Barn 0.9.2 includes the complete native macOS guest runtime in the Apple Silicon download and Homebrew installation. You can create Linux and macOS VMs after installing a …
-
Barn 0.9.1: Go 1.27.3 toolchain and Barn.app rename
Released on 2026-10-22. Barn 0.x releases are published via GitHub’s pre-release channel. For the latest release with a signed and notarized Barn.app in the Apple Silicon archive and Homebrew formula, see Barn 1.1.0. Barn 0.9.1 updates the Go …
Released on 2026-10-22. Barn 0.x releases are published via GitHub’s pre-release channel. For the latest release with a signed and notarized Barn.app in the Apple Silicon archive and Homebrew formula, see Barn 1.1.0. Barn 0.9.1 updates the Go …
-
Barn 0.9.0: native macOS guests and smoother Linux recovery
Released on 2026-09-30. Barn 0.9.0 manages both Linux labs and native macOS machines from a single CLI, while improving diagnostics and recovery after interrupted operations. For the latest release, see Barn 1.1.0. Install Barn · Download 0.9.0 …
Released on 2026-09-30. Barn 0.9.0 manages both Linux labs and native macOS machines from a single CLI, while improving diagnostics and recovery after interrupted operations. For the latest release, see Barn 1.1.0. Install Barn · Download 0.9.0 …
-
The Lifetime of a Native Mac VM
barn mac manages named macOS VMs through Apple’s Virtualization.framework, independently of the Linux inventory. Introduced in 0.9.0, it uses the native host app Barn.app, included in Apple Silicon release archives since 0.9.2. This essay distills …
barn mac manages named macOS VMs through Apple’s Virtualization.framework, independently of the Linux inventory. Introduced in 0.9.0, it uses the native host app Barn.app, included in Apple Silicon release archives since 0.9.2. This essay distills …
-
Barn 0.8.0: clearer recovery and refreshed images
Note Historical release record (0.8.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.8.0 cuts down on manual cleanup after interrupted host setup or partial VM starts, and refreshes the Debian and …
Note Historical release record (0.8.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.8.0 cuts down on manual cleanup after interrupted host setup or partial VM starts, and refreshes the Debian and …
-
Barn 0.7.0: simpler test labs and automatic recovery
Note Historical release record (0.7.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.7.0 streamlines first-run startup and recovery for local test labs: re-running barn up finishes interrupted work, …
Note Historical release record (0.7.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.7.0 streamlines first-run startup and recovery for local test labs: re-running barn up finishes interrupted work, …
-
Barn 0.6.0: Ubuntu 24.04 and smoother local labs
Note Historical release record (0.6.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.6.0 makes Ubuntu 24.04 the default guest image and improves planning, startup, scale-out, and node recreation for …
Note Historical release record (0.6.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.6.0 makes Ubuntu 24.04 the default guest image and improves planning, startup, scale-out, and node recreation for …
-
Barn 0.5.0: explicit disposal, explicit repositories, reproducible images
Note Historical release record (0.5.0). Official mirror failover was later added in 0.7.0, and the rm alias was removed in 0.9.0. Old release downloads are retired; see the CLI reference and installation guide for current usage. Barn 0.5.0 adds an …
Note Historical release record (0.5.0). Official mirror failover was later added in 0.7.0, and the rm alias was removed in 0.9.0. Old release downloads are retired; see the CLI reference and installation guide for current usage. Barn 0.5.0 adds an …
-
Barn 0.4.0: one command, working data disks, one voice
Note Historical release record (0.4.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.4.0 turns the first run into a single command, makes default data disks work out of the box on Debian and Ubuntu …
Note Historical release record (0.4.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.4.0 turns the first run into a single command, makes default data disks work out of the box on Debian and Ubuntu …
-
Barn 0.3.0: explicit catalogs and actionable readiness
Note Historical release record (0.3.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.3.0 replaces implicit catalog refreshes with explicit update commands, reports guest bootstrap failures per node, …
Note Historical release record (0.3.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.3.0 replaces implicit catalog refreshes with explicit update commands, reports guest bootstrap failures per node, …
-
Barn 0.2.0: selected convergence and release integrity
Note Historical release record (0.2.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.2.0 keeps the Pigsty inventory and on-disk deployment format introduced in 0.1.0 while fixing VPN route preflight …
Note Historical release record (0.2.0). Old release downloads are retired; use the installation guide for the current release. Barn 0.2.0 keeps the Pigsty inventory and on-disk deployment format introduced in 0.1.0 while fixing VPN route preflight …
-
repo.yaml Is Intent; catalog.json Is Evidence
This essay explains the Linux image repository contract in Barn 1.1.0 (macOS guests manage Apple .ipsw restore images and APFS base images separately via barn mac). A static VM image repository needs two kinds of metadata: human policy decisions …
This essay explains the Linux image repository contract in Barn 1.1.0 (macOS guests manage Apple .ipsw restore images and APFS base images separately via barn mac). A static VM image repository needs two kinds of metadata: human policy decisions …
-
A PID Is Not a Virtual Machine
This essay explains Linux runtime process identity and crash recovery in Barn 1.1.0. The separate native Mac lifecycle uses per-machine operation locks and runner protocol 2. A pidfile records a process ID at the moment it was written. Minutes or …
This essay explains Linux runtime process identity and crash recovery in Barn 1.1.0. The separate native Mac lifecycle uses per-machine operation locks and runner protocol 2. A pidfile records a process ID at the moment it was written. Minutes or …
-
Declarative Does Not Mean Destructive
This essay explains the Linux VM convergence model in Barn 1.1.0 (macOS guests are managed independently). A declarative tool compares live state against a configuration file—but in daily development, that file might be temporarily edited for …
This essay explains the Linux VM convergence model in Barn 1.1.0 (macOS guests are managed independently). A declarative tool compares live state against a configuration file—but in daily development, that file might be temporarily edited for …
-
Why Every Barn Node Has Two NICs
This essay explains the Linux lab network architecture in Barn 1.1.0 (macOS guests use independent per-VM vmnet NAT subnets). A Pigsty inventory identifies every database node by a stable IPv4 address: PostgreSQL streaming replication, Patroni/etcd …
This essay explains the Linux lab network architecture in Barn 1.1.0 (macOS guests use independent per-VM vmnet NAT subnets). A Pigsty inventory identifies every database node by a stable IPv4 address: PostgreSQL streaming replication, Patroni/etcd …
-
Why Barn Has No Projects
This essay explains the Linux lab deployment model in Barn 1.1.0 (macOS guests are managed as independent named VMs). Early prototypes of Barn treated every working directory as a separate project: a hidden directory marker identified the project, a …
This essay explains the Linux lab deployment model in Barn 1.1.0 (macOS guests are managed as independent named VMs). Early prototypes of Barn treated every working directory as a separate project: a hidden directory marker identified the project, a …
-
RC6 development candidate: owner-scoped Tier-1 delivery
Note Pre-Barn historical archive (Piglet 1.0.0-rc.6, 2026-08-25). This candidate was a local verification milestone and was never published as a GitHub Release or package repository; the SHA-256 digests below record the retained local build …
Note Pre-Barn historical archive (Piglet 1.0.0-rc.6, 2026-08-25). This candidate was a local verification milestone and was never published as a GitHub Release or package repository; the SHA-256 digests below record the retained local build …
-
Development snapshot: the Go 1.27 product surface
Note Pre-Barn historical archive (Piglet, 2026-08-24). At this snapshot there was no public release tag, signed production artifact, or package repository, and all embedded image records were marked testing. For current Barn behavior and support …
Note Pre-Barn historical archive (Piglet, 2026-08-24). At this snapshot there was no public release tag, signed production artifact, or package repository, and all embedded image records were marked testing. For current Barn behavior and support …