oib/aitbc
1
0
Fork 0
Code Issues Pull Requests Actions 7 Packages Projects Releases Wiki Activity
741 Commits 1 Branch 2 Tags
aae3111d178a7710ebc172363b86afa293da7611
Commit Graph

14 Commits

Author SHA1 Message Date
aitbc
aae3111d17 fix: remove duplicate /var/log/aitbc directory creation in setup script 
Directory Setup Cleanup - Complete:
✅ DUPLICATE DIRECTORY REMOVED: Eliminated redundant /var/log/aitbc directory creation
- setup.sh: Removed /var/log/aitbc from directories array and permissions/ownership
- Reason: ln -sf /var/lib/aitbc/logs /var/log/aitbc symlink replaces the directory
- Impact: Cleaner setup process without redundant operations

✅ BEFORE vs AFTER:
❌ Before (Redundant):
   directories=(
       "/var/lib/aitbc/logs"
       "/var/log/aitbc"  # ← Duplicate
   )
   chmod 755 /var/lib/aitbc/logs
   chmod 755 /var/log/aitbc  # ← Duplicate
   chown root:root /var/lib/aitbc/logs
   chown root:root /var/log/aitbc  # ← Duplicate
   ln -sf /var/lib/aitbc/logs /var/log/aitbc  # ← Replaces directory

✅ After (Clean):
   directories=(
       "/var/lib/aitbc/logs"
       # /var/log/aitbc created by symlink
   )
   chmod 755 /var/lib/aitbc/logs
   # Permissions for /var/log/aitbc inherited from source
   chown root:root /var/lib/aitbc/logs
   # Ownership for /var/log/aitbc inherited from source
   ln -sf /var/lib/aitbc/logs /var/log/aitbc  # ← Creates symlink

✅ SYMLINK BEHAVIOR:
🔗 ln -sf: Force symlink creation replaces existing directory
📁 Source: /var/lib/aitbc/logs (with proper permissions)
📁 Target: /var/log/aitbc (symlink to source)
🎯 Result: /var/log/aitbc inherits permissions from source directory

✅ CLEANUP BENEFITS:
✅ No Redundancy: Directory not created before symlink replaces it
✅ Simpler Logic: Fewer operations in setup script
✅ Correct Permissions: Symlink inherits from source directory
✅ Cleaner Code: Removed duplicate chmod/chown operations
✅ Proper Flow: Create source directory, then create symlink

✅ TECHNICAL CORRECTNESS:
✅ Symlink Precedence: ln -sf replaces existing files/directories
✅ Permission Inheritance: Symlink inherits source permissions
✅ Ownership Inheritance: Symlink inherits source ownership
✅ Standard Practice: Create source first, then symlink
✅ No Conflicts: No directory vs symlink conflicts

✅ FINAL DIRECTORY STRUCTURE:
📁 /var/lib/aitbc/logs/ (actual directory with permissions)
📁 /var/log/aitbc -> /var/lib/aitbc/logs/ (symlink)
📁 Both paths point to same location
🎯 No duplication or conflicts

RESULT: Successfully removed duplicate /var/log/aitbc directory creation, relying on the symlink to create the standard logging location with proper permission inheritance from the source directory.
 2026-03-30 17:33:05 +02:00
aitbc
da526f285a fix: remove SSH fallback for GitHub cloning, use HTTPS only 
GitHub Clone Simplification - Complete:
✅ SSH FALLBACK REMOVED: Simplified repository cloning to use HTTPS only
- setup.sh: Removed git@github.com SSH fallback that requires SSH keys
- Reason: Most users don't have GitHub SSH keys or accounts
- Impact: More accessible setup for all users

✅ BEFORE vs AFTER:
❌ Before: HTTPS with SSH fallback
   git clone https://github.com/aitbc/aitbc.git aitbc || {
       git clone git@github.com:aitbc/aitbc.git aitbc || error "Failed to clone repository"
   }
   - Required SSH keys for fallback
   - GitHub account needed for SSH access
   - Complex error handling

✅ After: HTTPS only
   git clone https://github.com/aitbc/aitbc.git aitbc || error "Failed to clone repository"
   - No SSH keys required
   - Public repository access
   - Simple and reliable
   - Works for all users

✅ ACCESSIBILITY IMPROVEMENTS:
🌐 Public Access: HTTPS works for everyone without authentication
🔑 No SSH Keys: No need to generate and configure SSH keys
📦 No GitHub Account: Works without personal GitHub account
🚀 Simpler Setup: Fewer configuration requirements
🎯 Universal Compatibility: Works on all systems and networks

✅ TECHNICAL BENEFITS:
✅ Reliability: HTTPS is more reliable across different networks
✅ Security: HTTPS is secure and appropriate for public repositories
✅ Simplicity: Single method, no complex fallback logic
✅ Debugging: Easier to troubleshoot connection issues
✅ Firewalls: HTTPS works through most firewalls and proxies

✅ USER EXPERIENCE:
✅ Lower Barrier: No SSH setup required
✅ Faster Setup: Fewer prerequisites
✅ Clear Errors: Single error message for failures
✅ Documentation: Simpler to document and explain
✅ Consistency: Same method as documented in README

✅ JUSTIFICATION:
📦 Public Repository: AITBC is public, no authentication needed
🔧 Setup Script: Should work out-of-the-box for maximum accessibility
🌐 Broad Audience: Open source project should be easy to set up
🎯 Simplicity: Remove unnecessary complexity
📚 Documentation: Matches public repository access methods

RESULT: Successfully simplified GitHub cloning to use HTTPS only, removing SSH key requirements and making the setup accessible to all users without GitHub accounts or SSH configuration.
 2026-03-30 17:32:13 +02:00
aitbc
3e0c3f2fa4 fix: update Node.js minimum requirement to 24.14.0+ to match JavaScript SDK 
Node.js Requirement Update - Complete:
✅ NODE.JS MINIMUM VERSION UPDATED: Changed from 18.0.0+ to 24.14.0+
- setup.sh: Updated Node.js version check to require 24.14.0+
- Reason: JavaScript SDK specifically requires Node.js 24.14.0+
- Impact: Ensures full compatibility with all JavaScript components

✅ VERSION REQUIREMENT ANALYSIS:
📦 JavaScript SDK: packages/js/aitbc-sdk/ requires Node.js 24.14.0+
🔧 Smart Contracts: packages/solidity/aitbc-token/ requires Node.js 18.0.0+
⚡ ZK Circuits: JavaScript components work with 24.14.0+
🎯 Decision: Use highest requirement for full functionality

✅ BEFORE vs AFTER:
❌ Before: Node.js 18.0.0+ (lowest common denominator)
   - Would work for smart contracts but not JavaScript SDK
   - Could cause SDK build failures
   - Inconsistent development experience

✅ After: Node.js 24.14.0+ (actual requirement)
   - Ensures JavaScript SDK builds successfully
   - Compatible with all components
   - Consistent development environment
   - Your v24.14.0 meets requirement exactly

✅ REQUIREMENTS SUMMARY:
🐍 Python: 3.13.5+ (core services)
🟢 Node.js: 24.14.0+ (JavaScript SDK, smart contracts, ZK circuits)
📦 npm: Required with Node.js
🔧 git: Version control
🔧 systemctl: Service management

✅ JUSTIFICATION:
📚 SDK Compatibility: JavaScript SDK specifically targets 24.14.0+
🔧 Modern Features: Latest Node.js features and security updates
🚀 Performance: Optimized performance for JavaScript components
📦 Package Support: Latest npm package compatibility
🎯 Future-Proof: Ensures compatibility with upcoming features

RESULT: Successfully updated Node.js minimum requirement to 24.14.0+ to match the JavaScript SDK requirement, ensuring full compatibility with all JavaScript components while your current version meets the requirement exactly.
 2026-03-30 17:31:23 +02:00
aitbc
209eedbb32 feat: add Node.js and npm to setup prerequisites 
Node.js Prerequisites Addition - Complete:
✅ NODE.JS REQUIREMENTS ADDED: Added Node.js and npm to setup prerequisites check
- setup.sh: Added node and npm command availability checks
- setup.sh: Added Node.js version validation (18.0.0+ required)
- Reason: Node.js is essential for JavaScript SDK and smart contract development

✅ NODE.JS USAGE ANALYSIS:
📦 JavaScript SDK: packages/js/aitbc-sdk/ requires Node.js 24.14.0+
🔧 Smart Contracts: packages/solidity/aitbc-token/ uses Hardhat framework
⚡ ZK Circuits: JavaScript witness generation and calculation
🛠️ Development Tools: TypeScript compilation, testing, linting

✅ PREREQUISITE CHECKS ADDED:
🔧 Tool Availability: Added 'command -v node' and 'command -v npm'
📋 Version Validation: Node.js 18.0.0+ (minimum for all components)
🎯 Compatibility: Your v24.14.0 exceeds requirements
📊 Error Handling: Clear error messages for missing tools

✅ VERSION REQUIREMENTS:
🐍 Python: 3.13.5+ (existing)
🟢 Node.js: 18.0.0+ (newly added)
📦 npm: Required with Node.js
🔧 systemd: Required for service management

✅ COMPONENTS REQUIRING NODE.JS:
📚 JavaScript SDK: Frontend/client integration library
🔗 Smart Contracts: Hardhat development framework
⚡ ZK Proof Generation: JavaScript witness calculators
🧪 Development: TypeScript compilation and testing
📦 Package Management: npm for JavaScript dependencies

✅ BENEFITS:
✅ Complete Prerequisites: All required tools checked upfront
✅ Version Validation: Ensures compatibility with project requirements
✅ Clear Errors: Helpful messages for missing or outdated tools
✅ Developer Experience: Early detection of environment issues
✅ Documentation: Explicit Node.js requirement documented

RESULT: Successfully added Node.js and npm to setup prerequisites, ensuring all required development tools are validated before installation begins. Your Node.js v24.14.0 exceeds the 18.0.0+ requirement.
 2026-03-30 17:31:00 +02:00
aitbc
26c3755697 refactor: remove redundant startup script and use systemd services directly 
SystemD Simplification - Complete:
✅ REDUNDANT STARTUP SCRIPT REMOVED: Eliminated unnecessary manual startup script
- setup.sh: Removed create_startup_script function entirely
- Reason: SystemD services are used directly, making manual startup script redundant
- Impact: Simplified setup process and eliminated unnecessary file creation

✅ FUNCTIONS REMOVED:
🗑️ create_startup_script: No longer needed with systemd services
🗑️ /opt/aitbc/start-services.sh: File is no longer created
🗑️ aitbc-startup.service: No longer needed for auto-start

✅ UPDATED WORKFLOW:
📋 Main function: Removed create_startup_script call
📋 Auto-start: Services enabled directly with systemctl enable
📋 Management: Updated commands to use systemctl
📋 Logging: Updated to use journalctl instead of tail

✅ SIMPLIFIED AUTO-START:
🔧 Before: Created aitbc-startup.service that called start-services.sh
🔧 After: Direct systemctl enable for each service
🎯 Benefit: Cleaner, more direct systemd integration
📁 Services: aitbc-wallet, aitbc-coordinator-api, aitbc-exchange-api, aitbc-blockchain-rpc

✅ UPDATED MANAGEMENT COMMANDS:
📋 Before: /opt/aitbc/start-services.sh
📋 After: systemctl restart aitbc-wallet aitbc-coordinator-api aitbc-exchange-api
📋 Before: tail -f /var/lib/aitbc/logs/aitbc-*.log
📋 After: journalctl -u aitbc-wallet -f
🎯 Purpose: Modern systemd-based service management

✅ CLEANER SETUP PROCESS:
1. Install systemd services (symbolic links)
2. Create health check script
3. Start services directly with systemctl
4. Enable services for auto-start
5. Complete setup with systemd-managed services

✅ BENEFITS ACHIEVED:
✅ Simplicity: No unnecessary intermediate scripts
✅ Direct Management: Services managed directly by systemd
✅ Modern Practice: Uses standard systemd service management
✅ Less Complexity: Fewer files and functions to maintain
✅ Better Integration: Full systemd ecosystem utilization

✅ CONSISTENT SYSTEMD APPROACH:
🔧 Service Installation: Symbolic links to /etc/systemd/system/
🔧 Service Management: systemctl start/stop/restart/enable
🔧 Service Monitoring: systemctl status and journalctl logs
🔧 Service Configuration: Service files in /opt/aitbc/systemd/

RESULT: Successfully removed redundant startup script and simplified the setup process to use systemd services directly, providing a cleaner, more modern, and maintainable service management approach.
 2026-03-30 17:29:45 +02:00
aitbc
7d7ea13075 fix: update startup script to use systemd services instead of manual process management 
SystemD Startup Update - Complete:
✅ STARTUP SCRIPT MODERNIZED: Changed from manual process management to systemd
- setup.sh: create_startup_script now uses systemctl commands instead of nohup and PID files
- Benefit: Proper service management with systemd instead of manual process handling
- Impact: Improved reliability, logging, and service management

✅ SYSTEMD ADVANTAGES OVER MANUAL MANAGEMENT:
🔧 Service Control: Proper start/stop/restart with systemctl
📝 Logging: Standardized logging through journald and systemd
🔄 Restart: Automatic restart on failure with service configuration
📊 Monitoring: Service status and health monitoring with systemctl
🔒 Security: Proper user permissions and service isolation

✅ BEFORE vs AFTER:
❌ Before (Manual Process Management):
   nohup python simple_daemon.py > /var/log/aitbc-wallet.log 2>&1 &
   echo  > /var/run/aitbc-wallet.pid
   source .venv/bin/activate (separate venvs)
   Manual PID file management
   No automatic restart

✅ After (SystemD Service Management):
   systemctl start aitbc-wallet.service
   systemctl enable aitbc-wallet.service
   Centralized logging and monitoring
   Automatic restart on failure
   Proper service lifecycle management

✅ UPDATED STARTUP SCRIPT FEATURES:
🚀 Service Start: systemctl start for all services
🔄 Service Enable: systemctl enable for auto-start
📊 Error Handling: Warning messages for failed services
🎯 Consistency: All services use same management approach
📝 Logging: Proper systemd logging integration

✅ SERVICES MANAGED:
🔧 aitbc-wallet.service: Wallet daemon service
🔧 aitbc-coordinator-api.service: Coordinator API service
🔧 aitbc-exchange-api.service: Exchange API service
🔧 aitbc-blockchain-rpc.service: Blockchain RPC service

✅ IMPROVED RELIABILITY:
✅ Automatic Restart: Services restart on failure
✅ Process Monitoring: SystemD monitors service health
✅ Resource Management: Proper resource limits and isolation
✅ Startup Order: Correct service dependency management
✅ Logging Integration: Centralized logging with journald

✅ MAINTENANCE BENEFITS:
✅ Standard Commands: systemctl start/stop/reload/restart
✅ Status Checking: systemctl status for service health
✅ Log Access: journalctl for service logs
✅ Configuration: Service files in /etc/systemd/system/
✅ Debugging: Better troubleshooting capabilities

RESULT: Successfully updated startup script to use systemd services, providing proper service management, automatic restart capabilities, and improved reliability over manual process management.
 2026-03-30 17:28:46 +02:00
aitbc
29f87bee74 fix: use symbolic links for systemd service files instead of copying 
SystemD Services Update - Complete:
✅ SERVICE INSTALLATION IMPROVED: Changed from copying to symbolic linking
- setup.sh: install_services function now uses ln -sf instead of cp
- Benefit: Service files automatically update when originals change
- Impact: Improved maintainability and consistency

✅ SYMBOLIC LINK ADVANTAGES:
🔗 Auto-Update: Changes to /opt/aitbc/systemd/*.service automatically reflected in /etc/systemd/system/
🔄 Synchronization: Installed services always match source files
📝 Maintenance: Single source of truth for service configurations
🎯 Consistency: No divergence between source and installed services

✅ BEFORE vs AFTER:
❌ Before: cp '/opt/aitbc/systemd/' /etc/systemd/system/
   - Static copies that don't update
   - Manual intervention required for updates
   - Potential divergence between source and installed

✅ After: ln -sf '/opt/aitbc/systemd/' /etc/systemd/system/
   - Dynamic symbolic links
   - Automatic updates when source changes
   - Always synchronized with source files

✅ TECHNICAL DETAILS:
🔗 ln -sf: Force symbolic link creation (overwrites existing)
📁 Source: /opt/aitbc/systemd/
📁 Target: /etc/systemd/system/
🔄 Update: Changes propagate automatically
🎯 Purpose: Maintain service configuration consistency

✅ MAINTENANCE BENEFITS:
✅ Single Source: Update only /opt/aitbc/systemd/ files
✅ Auto-Propagation: Changes automatically apply to installed services
✅ No Manual Sync: No need to manually copy updated files
✅ Consistent State: Installed services always match source

✅ USE CASES IMPROVED:
🔧 Service Updates: Configuration changes apply immediately
🔧 Debugging: Edit source files, changes reflect in running services
🔧 Development: Test service changes without re-copying
🔧 Deployment: Service updates propagate automatically

RESULT: Successfully changed systemd service installation to use symbolic links, ensuring automatic updates and eliminating potential configuration divergence between source and installed services.
 2026-03-30 17:28:10 +02:00
aitbc
0a976821f1 fix: update setup.sh to use central virtual environment instead of separate venvs 
Virtual Environment Consolidation - Complete:
✅ SETUP SCRIPT UPDATED: Changed from separate venvs to central virtual environment
- setup.sh: setup_venvs function now uses /opt/aitbc/venv instead of creating separate .venv for each service
- Added central venv creation with main requirements installation
- Consolidated all service dependencies into single virtual environment

✅ VIRTUAL ENVIRONMENT CHANGES:
🔧 Before: Separate .venv for each service (apps/wallet/.venv, apps/coordinator-api/.venv, apps/exchange/.venv)
🔧 After: Single central /opt/aitbc/venv for all services
📦 Dependencies: All service dependencies installed in central venv
🎯 Purpose: Consistent with recent virtual environment consolidation efforts

✅ SETUP FLOW IMPROVED:
📋 Central venv creation: Creates /opt/aitbc/venv if not exists
📋 Main requirements: Installs requirements.txt if present
📋 Service dependencies: Installs each service's requirements in central venv
📋 Consistency: Matches development environment using central venv

✅ BENEFITS ACHIEVED:
✅ Consistency: Setup script now matches development environment
✅ Efficiency: Single virtual environment instead of multiple separate ones
✅ Maintenance: Easier to manage and update dependencies
✅ Disk Space: Reduced duplication of Python packages
✅ Simplicity: Clearer virtual environment structure

✅ BACKWARD COMPATIBILITY:
🔄 Existing venv: If /opt/aitbc/venv exists, it's used instead of creating new
📋 Requirements: Main requirements.txt installed if available
📋 Services: Each service's requirements still installed properly
🎯 Functionality: All services work with central virtual environment

✅ UPDATED FUNCTION FLOW:
1. Check if central venv exists
2. Create central venv if needed with main requirements
3. Activate central venv
4. Install wallet service dependencies
5. Install coordinator API dependencies
6. Install exchange API dependencies
7. Complete setup with single virtual environment

RESULT: Successfully updated setup.sh to use central virtual environment, providing consistency with development environment and eliminating virtual environment duplication while maintaining all service functionality.
 2026-03-30 17:27:23 +02:00
aitbc
63308fc170 fix: update repository URLs from private Gitea to public GitHub 
Repository URL Update - Complete:
✅ REPOSITORY URLS UPDATED: Changed from private Gitea to public GitHub
- setup.sh: Updated clone URLs to use github.com/aitbc/aitbc
- docs/infrastructure/README.md: Updated manual setup instructions
- Reason: Gitea is private development-only, GitHub is public repository

✅ SETUP SCRIPT UPDATED:
🔧 Primary URL: https://github.com/aitbc/aitbc.git (public)
🔧 Fallback URL: git@github.com:aitbc/aitbc.git (SSH)
📁 Location: /opt/aitbc/setup.sh (clone_repo function)
🎯 Purpose: Public accessibility for all users

✅ DOCUMENTATION UPDATED:
📚 Infrastructure README: Updated manual setup instructions
📝 Before: sudo git clone https://gitea.bubuit.net/oib/aitbc.git /opt/aitbc
📝 After: sudo git clone https://github.com/aitbc/aitbc.git /opt/aitbc
🎯 Impact: Public accessibility for documentation

✅ PRESERVED DEVELOPMENT REFERENCES:
📊 scripts/monitoring/monitor-prs.py: Gitea API for development monitoring
📊 scripts/testing/qa-cycle.py: Gitea API for QA cycle
📊 scripts/utils/claim-task.py: Gitea API for task management
🎯 Context: These are internal development tools, should remain private

✅ URL CHANGE RATIONALE:
🌐 Public Access: GitHub repository is publicly accessible
🔒 Private Development: Gitea remains for internal development tools
📦 Setup Distribution: Public setup should use public repository
🎯 User Experience: Anyone can clone from GitHub without authentication

✅ IMPROVED USER EXPERIENCE:
✅ Public Accessibility: No authentication required for cloning
✅ Reliable Source: GitHub is more reliable for public access
✅ Clear Documentation: Updated instructions match actual URLs
✅ Development Separation: Private tools still use private Gitea

RESULT: Successfully updated repository URLs from private Gitea to public GitHub for public-facing setup and documentation while preserving internal development tool references to private Gitea.
 2026-03-30 17:26:11 +02:00
aitbc
3177801444 refactor: move setup.sh back to project root directory 
Setup Script Restoration - Complete:
✅ SETUP SCRIPT MOVED: Restored setup.sh to project root directory
- setup.sh: Moved from scripts/utils/ back to /opt/aitbc/ (project root)
- Reason: Main project setup script belongs in root for easy access
- Impact: Improves project setup experience and follows standard conventions

✅ ROOT DIRECTORY ENHANCED:
📁 setup.sh: Main project setup script (9.8KB)
📋 Purpose: Sets up AITBC services on new host with systemd
🔧 Functionality: Complete project initialization and configuration
📍 Location: Project root for maximum accessibility

✅ DOCUMENTATION UPDATED:
📚 Development Guidelines: Added setup.sh to essential root files
📖 Test Documentation: Updated to reference root setup.sh
🎯 Usage Instructions: Added ./setup.sh to test prerequisites
📝 Clear Guidance: Updated script location references

✅ SETUP SCRIPT CONTENTS:
🎯 Main Function: AITBC Local Setup Script
🔧 Features: Sets up AITBC services with systemd
📋 Capabilities: Service configuration, user setup, permissions
🎨 Interface: Colored output with logging functions
⚙️ Error Handling: Comprehensive error checking and reporting

✅ IMPROVED PROJECT STRUCTURE:
📁 Root Directory: Now contains essential setup.sh
📁 scripts/utils/: Contains utility scripts (not main setup)
📖 Documentation: Updated to reflect correct locations
🎯 User Experience: Easier project setup with ./setup.sh

✅ STANDARD PRACTICES:
📍 Root Location: Main setup scripts typically in project root
🔧 Easy Access: Developers expect ./setup.sh in root
📦 Complete Setup: Single script for full project initialization
🎯 First Step: Clear entry point for new developers

BENEFITS:
✅ Better UX: Easy to find and run ./setup.sh
✅ Standard Practice: Follows common project conventions
✅ Clear Entry Point: Single script for project setup
✅ Documentation: Updated to reflect correct locations
✅ Accessibility: Setup script in most accessible location

RESULT: Successfully moved setup.sh back to project root directory, improving project setup experience and following standard conventions while updating all relevant documentation.
 2026-03-30 17:24:41 +02:00
aitbc1
430120e94c chore: remove configuration files and reorganize production workflow documentation
Some checks failed
CLI Tests / test-cli (push) Failing after 6s
Details
Integration Tests / test-service-integration (push) Successful in 48s
Details
Documentation Validation / validate-docs (push) Successful in 11s
Details
Package Tests / test-python-packages (map[name:aitbc-core path:packages/py/aitbc-core]) (push) Successful in 32s
Details
Package Tests / test-python-packages (map[name:aitbc-agent-sdk path:packages/py/aitbc-agent-sdk]) (push) Successful in 46s
Details
Package Tests / test-python-packages (map[name:aitbc-crypto path:packages/py/aitbc-crypto]) (push) Successful in 24s
Details
Package Tests / test-python-packages (map[name:aitbc-sdk path:packages/py/aitbc-sdk]) (push) Successful in 25s
Details
Package Tests / test-javascript-packages (map[name:aitbc-sdk-js path:packages/js/aitbc-sdk]) (push) Successful in 19s
Details
Python Tests / test-python (push) Failing after 5s
Details
Package Tests / test-javascript-packages (map[name:aitbc-token path:packages/solidity/aitbc-token]) (push) Successful in 1m4s
Details
Security Scanning / security-scan (push) Successful in 31s
Details 
🧹 Configuration Cleanup:
• Remove .aitbc.yaml test configuration file
• Remove .editorconfig editor settings
• Remove .env.example environment template
• Remove .gitea-token authentication file
• Remove .pre-commit-config.yaml hooks configuration

📋 Workflow Documentation Restructuring:
• Replace immediate actions with complete optimization workflow (step 1)
• Add production deployment workflow as
 2026-03-29 20:06:51 +02:00
aitbc1
3352d63f36 feat: major infrastructure refactoring and optimization
All checks were successful
AITBC CLI Level 1 Commands Test / test-cli-level1 (push) Successful in 16s
Details
api-endpoint-tests / test-api-endpoints (push) Successful in 35s
Details
integration-tests / test-service-integration (push) Successful in 1m25s
Details
package-tests / test-python-packages (map[name:aitbc-agent-sdk path:packages/py/aitbc-agent-sdk python_version:3.13]) (push) Successful in 16s
Details
package-tests / test-python-packages (map[name:aitbc-cli path:. python_version:3.13]) (push) Successful in 14s
Details
package-tests / test-python-packages (map[name:aitbc-core path:packages/py/aitbc-core python_version:3.13]) (push) Successful in 13s
Details
package-tests / test-python-packages (map[name:aitbc-crypto path:packages/py/aitbc-crypto python_version:3.13]) (push) Successful in 10s
Details
package-tests / test-python-packages (map[name:aitbc-sdk path:packages/py/aitbc-sdk python_version:3.13]) (push) Successful in 12s
Details
package-tests / test-javascript-packages (map[name:aitbc-sdk node_version:24 path:packages/js/aitbc-sdk]) (push) Successful in 18s
Details
python-tests / test-specific (push) Has been skipped
Details
security-scanning / audit (push) Successful in 14s
Details
systemd-sync / sync-systemd (push) Successful in 4s
Details
package-tests / cross-language-compatibility (push) Successful in 2s
Details
package-tests / package-integration-tests (push) Successful in 3s
Details
Documentation Validation / validate-docs (push) Successful in 6m13s
Details
python-tests / test (push) Successful in 14s
Details 
## 🚀 Central Virtual Environment Implementation
- Created central venv at /opt/aitbc/venv for all services
- Updated 34+ systemd services to use central python interpreter
- Fixed PYTHONPATH configurations for proper module imports
- Created aitbc-env wrapper script for environment management

## 📦 Requirements Management Overhaul
- Consolidated 8 separate requirements.txt files into central requirements.txt
- Added web3>=6.11.0 for blockchain functionality
- Created automated requirements migrator tool (scripts/requirements_migrator.py)
- Established modular requirements structure (requirements-modules/)
- Generated comprehensive migration reports and documentation

## 🔧 Service Configuration Fixes
- Fixed Adaptive Learning service domain imports (AgentStatus)
- Resolved logging conflicts in zk_proofs and adaptive_learning_health
- Created missing data modules (consumer_gpu_profiles.py)
- Updated CLI to version 0.2.2 with proper import handling
- Fixed infinite loop in CLI alias configuration

## 📡 Port Mapping and Service Updates
- Updated blockchain node port from 8545 to 8005
- Added Adaptive Learning service on port 8010
- Consolidated P2P/sync into blockchain-node service
- All 5 core services now operational and responding

## 📚 Documentation Enhancements
- Updated SYSTEMD_SERVICES.md for Debian root usage (no sudo)
- Added comprehensive VIRTUAL_ENVIRONMENT.md guide
- Created REQUIREMENTS_MERGE_SUMMARY.md with migration details
- Updated RUNTIME_DIRECTORIES.md for standard Linux paths
- Fixed service port mappings and dependencies

## 🛠️ CLI Improvements
- Fixed import errors and version display (0.2.2)
- Resolved infinite loop in bashrc alias
- Added proper error handling for missing command modules
- Created aitbc-cli wrapper for clean execution

## ✅ Operational Status
- 5/5 AITBC services running successfully
- All health checks passing
- Central virtual environment fully functional
- Requirements management streamlined
- Documentation accurate and up-to-date

## 🎯 Technical Achievements
- Eliminated 7 redundant requirements.txt files
- Reduced service startup failures from 34+ to 0
- Established modular dependency management
- Created reusable migration tooling
- Standardized Debian root deployment practices

This represents a complete infrastructure modernization with improved reliability,
maintainability, and operational efficiency.
 2026-03-29 11:52:37 +02:00
aitbc1
1d7efb241d chore: update minimum Python version to 3.13.5 
- Update prerequisites check in setup.sh
- Update documentation in SETUP.md
 2026-03-28 09:55:01 +01:00
aitbc1
1402f2b784 feat: add automated setup script for new hosts 
- Add setup.sh that handles complete AITBC installation
- Creates virtual environments and installs dependencies
- Installs systemd services with fallback manual startup
- Adds health check and management scripts
- Include comprehensive SETUP.md documentation
 2026-03-28 09:53:09 +01:00