<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workflow on Barn</title>
    <link>https://barn.pgsty.com/tags/workflow/</link>
    <description>Recent content in Workflow on Barn</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Sun, 08 Nov 2026 00:00:00 +0800</lastBuildDate>
    
    
      <atom:link href="https://barn.pgsty.com/tags/workflow/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>What Barn Can Learn from Vagrant</title>
        <link>https://barn.pgsty.com/blog/design/vagrant-workflow-boundary/</link>
        <pubDate>Sun, 08 Nov 2026 10:00:00 +0800</pubDate>
        
        <guid>https://barn.pgsty.com/blog/design/vagrant-workflow-boundary/</guid>
        <description>&lt;p&gt;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 setup steps, move source and build artifacts, record the environment, and return to a known state.&lt;/p&gt;&#xA;&lt;p&gt;This is a design proposal based on the Barn source reviewed on &lt;strong&gt;2026-11-08&lt;/strong&gt;. The priorities below are candidates for implementation, with no assigned release or delivery date. Current commands are documented in the &lt;a href=&#34;https://barn.pgsty.com/docs/reference/cli/&#34;&gt;CLI reference&lt;/a&gt;.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
