<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Falcon on Solo</title><link>https://solo.hiero.org/tags/falcon/</link><description>Recent content in Falcon on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/falcon/index.xml" rel="self" type="application/rss+xml"/><item><title>One-shot Falcon Deployment</title><link>https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-deployment/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-deployment/</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;One-shot Falcon deployment is Solo&amp;rsquo;s YAML-driven one-shot workflow. It uses the same core
deployment pipeline as &lt;code&gt;solo one-shot single deploy&lt;/code&gt;, but lets you inject
component-specific flags through a single values file.&lt;/p&gt;
&lt;p&gt;One-shot use Falcon deployment when you need a repeatable advanced setup, want to check a
complete deployment into source control, or need to customise component flags
without running every Solo command manually.&lt;/p&gt;
&lt;p&gt;Falcon is especially useful for:&lt;/p&gt;</description></item><item><title>Falcon Values File Reference</title><link>https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-flags-reference/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-flags-reference/</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;This page catalogs the Solo CLI flags accepted under each top-level section of a
Falcon values file. Each entry corresponds to the command-line flag that the
underlying Solo subcommand accepts.&lt;/p&gt;
&lt;p&gt;Sections map to subcommands as follows:&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Section&lt;/th&gt;
 &lt;th&gt;Solo subcommand&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;network&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo consensus network deploy&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;setup&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo consensus node setup&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;consensusNode&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo consensus node start&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;mirrorNode&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo mirror node add&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;explorerNode&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo explorer node add&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;relayNode&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo relay node add&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;blockNode&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;&lt;code&gt;solo block node add&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;All flag names must be written in long form with double dashes (for example,
&lt;code&gt;--release-tag&lt;/code&gt;). Flags left empty (&lt;code&gt;&amp;quot;&amp;quot;&lt;/code&gt;) or matching their default value are
ignored by Solo at argument expansion time.&lt;/p&gt;</description></item></channel></rss>