Environment Setup and Agent Install
This page covers first-time environment setup for cloud-edge execution.
Step 1: Create Environment Record
In project environments UI, create an environment with:
- clear name (location + purpose)
- environment type (
edge/on-premwhere applicable) - connection notes for operations
Do not reuse one environment entry across multiple physical devices.
Step 2: Capture Environment ID
After creation, copy the generated environment ID.
This ID binds the runtime agent to the correct project target.
Step 3: Install Agent Container
Run the environment agent in Docker with restart policy enabled.
Typical command pattern:
docker run -d \
--name solutionengine-agent \
--restart unless-stopped \
-e ENV_ID=<environment_id> \
-e API_URL=<platform_api_url> \
-e AUTH_TOKEN=<scoped_token> \
solutionengine/solutionengine_agent:latest
Required Runtime Settings
| Variable | Required | Purpose |
|---|---|---|
ENV_ID | Yes | Binds agent to target environment |
API_URL | Yes | Platform API endpoint |
AUTH_TOKEN | Yes | Agent authentication |
SYNC_INTERVAL | Optional | Workflow sync cadence |
HEARTBEAT_INTERVAL | Optional | Health reporting cadence |
Validation Checklist
- Container is running (
docker ps) - First heartbeat appears in environment status
- Environment status changes to online
- Assigned workflows synchronize successfully
Common Setup Failures
- Wrong environment ID
- Invalid token/scope
- API endpoint unreachable from target network
- Container restarted repeatedly due to missing env vars
