Merge pull request #944 from adionit7/docs/remove-docker-compose-references
docs: remove outdated Docker Compose references
This commit is contained in:
@@ -8,7 +8,6 @@
|
||||
/hive/ @adenhq/maintainers
|
||||
|
||||
# Infrastructure
|
||||
/docker-compose*.yml @adenhq/maintainers
|
||||
/.github/ @adenhq/maintainers
|
||||
|
||||
# Documentation
|
||||
|
||||
+1
-1
@@ -352,7 +352,7 @@ Aden은 모니터링과 관측성을 위해 토큰 사용량, 지연 시간 메
|
||||
|
||||
**Q: Aden은 어떤 배포 방식을 지원하나요?**
|
||||
|
||||
Aden은 기본적으로 Docker Compose 배포를 지원하며, 프로덕션 및 개발 환경 설정을 모두 제공합니다. Docker를 지원하는 모든 인프라에서 셀프 호스팅이 가능합니다. 클라우드 배포 옵션과 Kubernetes 대응 설정은 로드맵에 포함되어 있습니다.
|
||||
Aden은 Python 패키지를 통한 셀프 호스팅 배포를 지원합니다. 설치 방법은 [환경 설정 가이드](ENVIRONMENT_SETUP.md)를 참조하세요. 클라우드 배포 옵션과 Kubernetes 대응 설정은 로드맵에 포함되어 있습니다.
|
||||
|
||||
**Q: Aden은 복잡한 프로덕션 규모의 사용 사례도 처리할 수 있나요?**
|
||||
|
||||
|
||||
@@ -351,7 +351,7 @@ Aden collects telemetry data for monitoring and observability purposes, includin
|
||||
|
||||
**Q: What deployment options does Aden support?**
|
||||
|
||||
Aden supports Docker Compose deployment out of the box, with both production and development configurations. Self-hosted deployments work on any infrastructure supporting Docker. Cloud deployment options and Kubernetes-ready configurations are on the roadmap.
|
||||
Aden supports self-hosted deployments via Python packages. See the [Environment Setup Guide](ENVIRONMENT_SETUP.md) for installation instructions. Cloud deployment options and Kubernetes-ready configurations are on the roadmap.
|
||||
|
||||
**Q: Can Aden handle complex, production-scale use cases?**
|
||||
|
||||
|
||||
+2
-23
@@ -6,7 +6,7 @@ Hive uses a centralized configuration system based on a single `config.yaml` fil
|
||||
|
||||
```
|
||||
config.yaml --> generate-env.ts --> .env files
|
||||
├── .env (root, for Docker)
|
||||
├── .env (root)
|
||||
├── honeycomb/.env (frontend)
|
||||
└── hive/.env (backend)
|
||||
```
|
||||
@@ -132,18 +132,6 @@ cp config.yaml.example config.production.yaml
|
||||
# Edit for production settings
|
||||
```
|
||||
|
||||
## Docker Compose Integration
|
||||
|
||||
The root `.env` file is used by Docker Compose. Key variables:
|
||||
|
||||
| Variable | Description | Default |
|
||||
|----------|-------------|---------|
|
||||
| `FRONTEND_PORT` | Frontend container port | 3000 |
|
||||
| `BACKEND_PORT` | Backend container port | 4000 |
|
||||
| `NODE_ENV` | Node environment | production |
|
||||
| `DATABASE_URL` | Database connection | - |
|
||||
| `JWT_SECRET` | Auth secret key | - |
|
||||
|
||||
## Security Best Practices
|
||||
|
||||
1. **Never commit `config.yaml`** - It may contain secrets
|
||||
@@ -158,11 +146,6 @@ After changing `config.yaml`:
|
||||
```bash
|
||||
# Regenerate .env files
|
||||
npm run generate:env
|
||||
|
||||
# Restart services
|
||||
docker compose restart
|
||||
# or
|
||||
docker compose up --build
|
||||
```
|
||||
|
||||
## Troubleshooting
|
||||
@@ -175,11 +158,7 @@ docker compose up --build
|
||||
|
||||
### Configuration Validation Errors
|
||||
|
||||
The backend validates configuration on startup. Check logs for specific errors:
|
||||
|
||||
```bash
|
||||
docker compose logs hive
|
||||
```
|
||||
The backend validates configuration on startup. Check logs for specific errors.
|
||||
|
||||
### Missing Environment Variables
|
||||
|
||||
|
||||
@@ -83,13 +83,13 @@ Answer these questions:
|
||||
1. What is the main frontend folder called?
|
||||
2. What is the main backend folder called?
|
||||
3. What file would you edit to configure the application?
|
||||
4. What's the Docker command to start all services (hint: check README)?
|
||||
4. What's the command to set up the Python environment (hint: check README)?
|
||||
|
||||
### Task 3.2: Find the Features 🎯
|
||||
Look through the codebase to find:
|
||||
|
||||
1. Where are the MCP tools defined? (provide the file path)
|
||||
2. What port does the API run on? (hint: check README or docker-compose)
|
||||
2. What port does the MCP server run on? (hint: check the tools/Dockerfile)
|
||||
3. Find one TypeScript interface related to agents (provide file path and interface name)
|
||||
|
||||
---
|
||||
|
||||
@@ -13,11 +13,11 @@ Master the deployment and operations of AI agent infrastructure! This challenge
|
||||
### Task 1.1: Docker Deep Dive 🐳
|
||||
Analyze the Aden Docker setup:
|
||||
|
||||
1. List all services defined in `docker-compose.yml`
|
||||
2. What's the purpose of `docker-compose.override.yml`?
|
||||
1. What Dockerfile exists in the repository and what does it build?
|
||||
2. How would you containerize the MCP tools server?
|
||||
3. How is hot reload enabled for development?
|
||||
4. What volumes are mounted and why?
|
||||
5. What networking mode is used between services?
|
||||
4. What would need to be mounted as volumes for persistence?
|
||||
5. What networking considerations exist for the MCP server?
|
||||
|
||||
### Task 1.2: Service Dependencies 🔗
|
||||
Map the service dependencies:
|
||||
|
||||
@@ -65,12 +65,6 @@ echo "Generating environment files from config.yaml..."
|
||||
npx tsx scripts/generate-env.ts
|
||||
echo "✓ Environment files generated"
|
||||
|
||||
# Create docker-compose.override.yml for development
|
||||
if [ ! -f "$PROJECT_ROOT/docker-compose.override.yml" ]; then
|
||||
cp "$PROJECT_ROOT/docker-compose.override.yml.example" "$PROJECT_ROOT/docker-compose.override.yml"
|
||||
echo "✓ Created docker-compose.override.yml for development"
|
||||
fi
|
||||
|
||||
echo ""
|
||||
echo "==================================="
|
||||
echo " Setup Complete (Legacy)"
|
||||
|
||||
Reference in New Issue
Block a user