<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Local-Build on Solo</title><link>https://solo.hiero.org/tags/local-build/</link><description>Recent content in Local-Build on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/local-build/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Solo</title><link>https://solo.hiero.org/docs/using-solo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/using-solo/</guid><description/></item><item><title>Deploying a Local Consensus Node Build</title><link>https://solo.hiero.org/docs/using-solo/local-builds/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/using-solo/local-builds/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Solo&amp;rsquo;s &lt;code&gt;--local-build-path&lt;/code&gt; flag lets you deploy a network using a consensus
node binary you compiled locally. Use this when you need to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Test unreleased hiero-consensus-node code against a live Solo network.&lt;/li&gt;
&lt;li&gt;Reproduce a bug with a specific build.&lt;/li&gt;
&lt;li&gt;Iterate on platform changes without a full release cycle.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Solo validates the path for the expected &lt;code&gt;apps/&lt;/code&gt; and &lt;code&gt;lib/&lt;/code&gt; subdirectories,
then uses &lt;code&gt;kubectl cp&lt;/code&gt; to push the local binaries directly into the running
node pods — no Docker image rebuild or registry push required.&lt;/p&gt;</description></item></channel></rss>