fix: remove API_PORT from container environment variables

The API_PORT variable was incorrectly included in the container's
environment section. It should only be used for host port mapping
in docker-compose.yml, not passed into the container.

Changes:
- Remove API_PORT from environment section in docker-compose.yml
- Container always uses port 8080 internally (hardcoded in entrypoint.sh)
- API_PORT in .env/.env.example only controls the host-side mapping:
  ports: "${API_PORT:-8080}:8080" (host:container)

Why this matters:
- Prevents confusion about whether API_PORT changes internal port
- Clarifies that entrypoint.sh hardcodes --port 8080
- Simplifies container environment (one less unused variable)
- More explicit about the port mapping behavior

No functional change - the container was already ignoring this variable.
This commit is contained in:
2025-10-31 14:38:53 -04:00
parent 849e7bffa2
commit c929080960
2 changed files with 5 additions and 7 deletions

View File

@@ -8,10 +8,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
### Changed
- **Simplified Configuration** - Removed `RUNTIME_ENV_PATH` environment variable
- No longer needed in docker-compose.yml or .env.example
- API mode dynamically manages runtime configs via `RuntimeConfigManager`
- Legacy tools gracefully handle missing `RUNTIME_ENV_PATH`
- **Simplified Configuration** - Removed unnecessary environment variables
- Removed `RUNTIME_ENV_PATH` (API dynamically manages runtime configs)
- Removed `API_PORT` from container environment (only used for host port mapping)
- Container always uses port 8080 internally (hardcoded in entrypoint.sh)
- API_PORT in .env only controls host-side port mapping
- Reduces configuration complexity for new deployments
## [0.3.0] - 2025-10-31

View File

@@ -24,9 +24,6 @@ services:
- TRADE_HTTP_PORT=8002
- GETPRICE_HTTP_PORT=8003
# API Configuration
- API_PORT=${API_PORT:-8080}
# Agent Configuration
- AGENT_MAX_STEP=${AGENT_MAX_STEP:-30}
ports: