<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Store on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/store/</link>
    <description>Recent content in Store on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/store/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CodeInstances Adds a Self-Hosted Store, Push and Pull by ID, and Bug Reports That Reproduce</title>
      <link>https://codeinstances.com/codeinstances-adds-a-self-hosted-store-push-and-pull-by-id-and-bug-reports-that-reproduce/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-adds-a-self-hosted-store-push-and-pull-by-id-and-bug-reports-that-reproduce/</guid>
      <description>&lt;p&gt;CodeInstances v0.5.0 is about getting a run from where it failed to where someone can fix it. A test fails in CI at 3 a.m. The run is kept, but it&amp;rsquo;s sitting on a build machine that&amp;rsquo;s gone in an hour. This release adds a small store of your own to keep runs in, &lt;code&gt;push&lt;/code&gt; and &lt;code&gt;pull&lt;/code&gt; to move them by id, and &lt;code&gt;report&lt;/code&gt;, which writes the bug report you paste into the issue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CodeInstances Runs Kept Instances on Demand, From a Store You Control</title>
      <link>https://codeinstances.com/codeinstances-runs-kept-instances-on-demand-from-a-store-you-control/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-runs-kept-instances-on-demand-from-a-store-you-control/</guid>
      <description>&lt;p&gt;CodeInstances v0.8.0 lets a store run what it keeps. Start it with &lt;code&gt;serve -run&lt;/code&gt;, and anyone with the store&amp;rsquo;s token can ask it to replay a run, or fork one at a step, and get back how it went. &lt;code&gt;codeinstances run 3f2a9c1e77b0&lt;/code&gt; replays that run on the store. &lt;code&gt;codeinstances run -at 4 -o what-if.instance 3f2a9c1e77b0&lt;/code&gt; forks it at call 4 there and downloads the result.&lt;/p&gt;&#xA;&lt;p&gt;Think of a function service, where code sits ready and a request runs it. Here the kept run is the function. A replay answers whether the program, as installed on that machine, still does what the run did. A fork tries the run again from a step, and nobody has to set the program up on their own laptop to do it. Every run is answered from the recording, so HTTP calls made through the proxy settings never go out.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
