docs: add hub-only warning to README and remove Docker removal summary

- Add prominent hub-only warning banner to README.md
- Link to HUB_STATUS.md for repository transition details
- Remove DOCKER_REMOVAL_SUMMARY.md documentation file
- Remove Docker removal statistics and policy compliance documentation
- Remove backup script references and removal results sections
This commit is contained in:
AITBC System
2026-03-23 10:46:01 +01:00
parent 4969972ed8
commit 9d11f659c8
2 changed files with 2 additions and 147 deletions

View File

@@ -1,5 +1,7 @@
# AITBC — AI Agent Compute Network 🤖
> 🚨 **IMPORTANT**: This repository is now a **hub-only** environment serving as a bridge between Gitea and GitHub. All local development services have been removed. See [HUB_STATUS.md](HUB_STATUS.md) for details.
**Share your GPU resources with AI agents in a decentralized network** 🚀
AITBC is a decentralized platform where AI agents can discover and utilize computational resources from providers. The network enables autonomous agents to collaborate, share resources, and build self-improving infrastructure through swarm intelligence.

View File

@@ -1,147 +0,0 @@
# Docker Removal Summary - March 18, 2026
## ✅ **DOCKER SUPPORT REMOVED**
Successfully removed all Docker-related files and references from the AITBC codebase in compliance with the strict NO DOCKER policy.
---
## 📊 **Removal Results**
### **Files Removed**: 2 main Docker files
### **Scripts Backed Up**: 2 deployment scripts
### **Policy Compliance**: 100% NO DOCKER policy maintained
---
## 🗑️ **Files Removed**
### **🐳 Main Docker Files**
-`Dockerfile` - Multi-stage build for AITBC CLI
-`docker-compose.yml` - Docker Compose configuration
### **📜 Scripts Backed Up (Not Deleted)**
- 📦 `scripts/deploy.sh``scripts/deploy.sh.docker_backup`
- 📦 `scripts/production-deploy.sh``scripts/production-deploy.sh.docker_backup`
---
## 🔍 **Docker References Analysis**
### **📊 Search Results**
- **Total Matches Found**: 393 across 143 files
- **Documentation Files**: 87 matches across 39 files
- **Script Files**: 50 matches across 4 files
- **Package Dependencies**: 200+ matches in virtual environments
### **📂 Categories of References**
#### **✅ Removed (Main Files)**
- Main Docker configuration files
- Docker Compose files
- Docker-specific deployment scripts
#### **📦 Package Dependencies (Left Intact)**
- Virtual environment package files (`.venv/`)
- Third-party package metadata
- Python package dependencies
- **Reason**: These are dependency files, not Docker configuration
#### **📚 Documentation References (Left Intact)**
- Historical documentation mentioning Docker
- Security audit references
- Development setup mentions
- **Reason**: Documentation references for historical context
#### **🔧 Script References (Backed Up)**
- Deployment scripts with Docker commands
- Production deployment scripts
- **Action**: Backed up with `.docker_backup` suffix
---
## 🎯 **NO DOCKER Policy Compliance**
### **✅ Policy Requirements Met**
- **No Docker files**: All main Docker files removed
- **No Docker configuration**: Docker Compose removed
- **No Docker deployment**: Scripts backed up, not active
- **Native Linux tools**: System uses native tools only
### **✅ Current Deployment Approach**
- **System Services**: systemd services instead of Docker containers
- **Native Tools**: Lynis, RKHunter, ClamAV, Nmap for security
- **Native Deployment**: Direct system deployment without containerization
- **Development Workflows**: Docker-free development environment
---
## 📋 **Remaining Docker References**
### **📚 Documentation (Historical)**
- Security audit documentation mentioning Docker scans
- Historical deployment documentation
- Development setup references
- **Status**: Left for historical context
### **📦 Package Dependencies (Automatic)**
- Python virtual environment packages
- Third-party library metadata
- Package manager files
- **Status**: Left intact (not Docker-specific)
### **🔧 Backup Scripts**
- `scripts/deploy.sh.docker_backup`
- `scripts/production-deploy.sh.docker_backup`
- **Status**: Backed up for reference, not active
---
## 🚀 **Impact Assessment**
### **✅ Zero Impact on Operations**
- **Services Continue**: All services run via systemd
- **Security Maintained**: Native security tools operational
- **Development Works**: Docker-free development environment
- **Deployment Ready**: Native deployment procedures in place
### **✅ Benefits Achieved**
- **Policy Compliance**: 100% NO DOCKER policy maintained
- **Clean Codebase**: No active Docker files
- **Native Performance**: Direct system resource usage
- **Security Simplicity**: Native security tools only
---
## 📊 **Final Status**
### **🗑️ Files Removed**: 4 total
- `Dockerfile`
- `docker-compose.yml`
- `scripts/deploy.sh.docker_backup`
- `scripts/production-deploy.sh.docker_backup`
### **📦 Backed Up Files**: 2 (REMOVED)
- `scripts/deploy.sh.docker_backup` → DELETED
- `scripts/production-deploy.sh.docker_backup` → DELETED
### **✅ Policy Compliance**: 100%
- No active Docker files
- No Docker configuration
- Native deployment only
- System services operational
---
## 🎉 **Removal Complete**
**Status**: ✅ **DOCKER SUPPORT FULLY REMOVED**
The AITBC codebase now fully complies with the strict NO DOCKER policy. All active Docker files have been removed, and the system operates entirely with native Linux tools and systemd services.
---
**Removal Date**: March 18, 2026
**Files Removed**: 4 total Docker-related files
**Policy Compliance**: 100% NO DOCKER
**Status**: DOCKER-FREE CODEBASE ACHIEVED