Skip to content

feat: Integrate OpenClaw for Site 2 - #68

Open
Farhan-Abbas wants to merge 2 commits into
denoslab:mainfrom
Farhan-Abbas:site-2-openclaw-add
Open

Farhan-Abbas wants to merge 2 commits into
denoslab:mainfrom
Farhan-Abbas:site-2-openclaw-add

Conversation

@Farhan-Abbas

Copy link
Copy Markdown
Collaborator

Solves #66

This PR adds the necessary orchestration and configuration to spin up an isolated OpenClaw LLM agent for Site 2.

Changes Included:

  • Added OpenClaw to Site 2 Stack:
    • Updated docker-compose.site2.yml with openclaw-site2 and openclaw-site2-perms services.
    • Added port mappings (18790:18789) and WebSocket allowed origins to prevent isolation clashes with the main workbench stack.
    • Created openclaw.site2.example.env as a base reference point for Site 2's agent.

Copilot AI review requested due to automatic review settings May 26, 2026 06:15

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds orchestration and configuration to run an isolated OpenClaw agent instance as part of the Site 2 controller stack, supporting multi-site workflows (Issue #66).

Changes:

  • Added openclaw-site2 and openclaw-site2-perms services to the Site 2 docker-compose stack, with dedicated volumes and host port mapping.
  • Added a Site 2 OpenClaw environment example file for configuring the agent.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
controller/docker-compose.site2.yml Introduces OpenClaw services/volumes for Site 2 and exposes the gateway/UI on a separate host port.
controller/.env.openclaw.site2.example Provides an example env configuration intended for the Site 2 OpenClaw instance.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

ports:
- '18790:18789'
env_file:
- openclaw.site2.env

@Farhan-Abbas Farhan-Abbas May 26, 2026 •

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be better to let the dev know in a readme on how to name environment the file

Comment on lines +97 to +112
ports:
- '18790:18789'
env_file:
- openclaw.site2.env
environment:
OPENCLAW_CONTROL_UI_ALLOWED_ORIGINS: "http://localhost:18790,http://127.0.0.1:18790,ws://localhost:18790,ws://127.0.0.1:18790"
PYTHONPATH: /home/node/.openclaw/workspace/starfish-cli
volumes:
- openclaw_config_site2:/home/node/.openclaw
- openclaw_workspace_site2:/home/node/.openclaw/workspace
- ../cli:/home/node/.openclaw/workspace/starfish-cli:ro
healthcheck:
test: ["CMD", "curl", "-fsS", "http://127.0.0.1:18789/healthz"]
interval: 10s
timeout: 5s
retries: 5
Comment on lines +1 to +2
# OpenClaw Configuration Site 2
OPENAI_API_KEY=your-openai-api-key-here

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants