docs: update AITBC CLI configuration in workflow
All checks were successful
Documentation Validation / validate-docs (push) Successful in 10s
All checks were successful
Documentation Validation / validate-docs (push) Successful in 10s
- Add prerequisite that CLI tool uses /etc/aitbc/blockchain.env by default - Add CLI integration note to environment configuration section - Clarify that CLI tool automatically uses central configuration file - Ensure workflow documentation reflects CLI tool's default behavior - Maintain consistency between directory structure and CLI usage
This commit is contained in:
@@ -13,6 +13,7 @@ This workflow sets up a two-node AITBC blockchain network (aitbc1 as genesis aut
|
|||||||
- Redis available for cross-node gossip
|
- Redis available for cross-node gossip
|
||||||
- Python venv at `/opt/aitbc/venv`
|
- Python venv at `/opt/aitbc/venv`
|
||||||
- AITBC CLI tool available (aliased as `aitbc`)
|
- AITBC CLI tool available (aliased as `aitbc`)
|
||||||
|
- CLI tool configured to use `/etc/aitbc/blockchain.env` by default
|
||||||
|
|
||||||
## Directory Structure
|
## Directory Structure
|
||||||
|
|
||||||
@@ -34,6 +35,7 @@ The workflow uses the central `/etc/aitbc/blockchain.env` file as the configurat
|
|||||||
- **Path Updates**: Paths are updated to use the standardized directory structure
|
- **Path Updates**: Paths are updated to use the standardized directory structure
|
||||||
- **Backup Strategy**: Original config is backed up before modifications
|
- **Backup Strategy**: Original config is backed up before modifications
|
||||||
- **Standard Location**: Config moved to `/etc/aitbc/` following system standards
|
- **Standard Location**: Config moved to `/etc/aitbc/` following system standards
|
||||||
|
- **CLI Integration**: AITBC CLI tool uses this config file by default
|
||||||
|
|
||||||
### 1. Prepare aitbc1 (Genesis Authority Node)
|
### 1. Prepare aitbc1 (Genesis Authority Node)
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user