oib/aitbc
1
0
Fork 0
Code Issues Pull Requests Actions 7 Packages Projects Releases Wiki Activity

refactor: consolidate duplicate environment files
Some checks failed
Documentation Validation / validate-docs (push) Has been cancelled
Details

Browse Source 
- Remove duplicate /etc/aitbc/blockchain.env file
- Consolidate to single /etc/aitbc/.env file
- Update all systemd services to use /etc/aitbc/.env
- Code already configured to use /etc/aitbc/.env
- Files were identical - no data loss
- Update workflow documentation to reflect single env file
- Both aitbc1 and aitbc nodes updated

This eliminates confusion and ensures both code and services
use the same environment file location.
This commit is contained in:
aitbc1
2026-03-29 15:58:16 +02:00
parent 9b92e7e2a5
commit b3066d5fb7
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.windsurf/workflows/multi-node-blockchain-setup.md
View File

@@ -34,6 +34,7 @@ systemctl daemon-reload
# 3. Create central configuration file # 3. Create central configuration file
cp /opt/aitbc/.env /etc/aitbc/.env.backup 2>/dev/null || true cp /opt/aitbc/.env /etc/aitbc/.env.backup 2>/dev/null || true
# Ensure .env is in the correct location (already should be)
mv /opt/aitbc/.env /etc/aitbc/.env 2>/dev/null || true mv /opt/aitbc/.env /etc/aitbc/.env 2>/dev/null || true
# 4. Setup AITBC CLI tool # 4. Setup AITBC CLI tool
@@ -53,7 +54,7 @@ chmod 600 /var/lib/aitbc/keystore/.password
# 7. Verify setup # 7. Verify setup
aitbc --help 2>/dev/null || echo "CLI available but limited commands" aitbc --help 2>/dev/null || echo "CLI available but limited commands"
ls -la /etc/aitbc/blockchain.env ls -la /etc/aitbc/.env
``` ```
## Directory Structure ## Directory Structure
@@ -69,7 +70,7 @@ ls -la /etc/aitbc/blockchain.env
### Environment Configuration ### Environment Configuration
The workflow uses the central `/etc/aitbc/.env` file as the configuration for both nodes: The workflow uses the single central `/etc/aitbc/.env` file as the configuration for both nodes:
- **Base Configuration**: The central config contains all default settings - **Base Configuration**: The central config contains all default settings
- **Node-Specific Adaptation**: Each node adapts the config for its role (genesis vs follower) - **Node-Specific Adaptation**: Each node adapts the config for its role (genesis vs follower)