Advanced Solo Setup on Solo

Using Environment Variables

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Solo supports a set of environment variables that let you customize its behaviour without modifying command-line flags on every run. Variables set in your shell environment take effect automatically for all subsequent Solo commands.

Tip: Add frequently used variables to your shell profile (e.g. ~/.zshrc or ~/.bashrc) to persist them across sessions.

General

Environment Variable	Description	Default Value
`SOLO_HOME`	Path to the Solo cache and log files	`~/.solo`
`SOLO_CACHE_DIR`	Path to the Solo cache directory	`~/.solo/cache`
`SOLO_LOG_LEVEL`	Logging level for Solo operations. Accepted values: `trace`, `debug`, `info`, `warn`, `error`	`info`
`SOLO_DEV_OUTPUT`	Treat all commands as if the `--dev` flag were specified	`false`
`SOLO_CHAIN_ID`	Chain ID of the Solo network	`298`
`FORCE_PODMAN`	Force the use of Podman as the container engine when creating a new local cluster. Accepted values: `true`, `false`	`false`

Network and Node Identity

Environment Variable	Description	Default Value
`DEFAULT_START_ID_NUMBER`	First node account ID of the Solo test network	`0.0.3`
`SOLO_NODE_INTERNAL_GOSSIP_PORT`	Internal gossip port used by the Hiero network	`50111`
`SOLO_NODE_EXTERNAL_GOSSIP_PORT`	External gossip port used by the Hiero network	`50111`
`SOLO_NODE_DEFAULT_STAKE_AMOUNT`	Default stake amount for a node	`500`
`GRPC_PORT`	gRPC port used for local node communication	`50211`
`LOCAL_NODE_START_PORT`	Local node start port for the Solo network	`30212`
`SOLO_CHAIN_ID`	Chain ID of the Solo network	`298`

Operator and Key Configuration

Environment Variable	Description	Default Value
`SOLO_OPERATOR_ID`	Operator account ID for the Solo network	`0.0.2`
`SOLO_OPERATOR_KEY`	Operator private key for the Solo network	`302e020100...`
`SOLO_OPERATOR_PUBLIC_KEY`	Operator public key for the Solo network	`302a300506...`
`FREEZE_ADMIN_ACCOUNT`	Freeze admin account ID for the Solo network	`0.0.58`
`GENESIS_KEY`	Genesis private key for the Solo network	`302e020100...`

Note: Full key values are omitted above for readability. Refer to the source defaults for complete key strings.

Customizing Solo with Tasks

Mon, 01 Jan 0001 00:00:00 +0000

Overview

The Task tool (task) is a task runner that enables you to deploy and customize Solo networks using infrastructure-as-code patterns. Rather than running individual Solo CLI commands, you can use predefined Taskfile targets to orchestrate complex deployment workflows with a single command.

This guide covers installing the Task tool, understanding available Taskfile targets, and using them to deploy networks with various configurations. It also points to maintained example projects that demonstrate common Solo workflows.

Solo CI Workflow

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This guide walks you through integrating Solo into a GitHub Actions CI pipeline - covering runner requirements, tool installation, and automated network deployment. Each step installs dependencies directly in the workflow, since CI runners are fresh environments with no pre-installed tools.

Prerequisites

Before proceeding, ensure you have completed the following:

System Readiness — your local environment meets all hardware and software requirements.
Quickstart — you are familiar with the basic Solo workflow and the solo one-shot single deploy command.

This guide assumes you are integrating Solo into a GitHub Actions workflow where each runner is a fresh environment. The steps below install all required tools directly inside the workflow rather than relying on pre-installed dependencies.