chore: merge main and resolve conflicts in http_provider.go
This commit is contained in:
parent
c1e02e7898
commit
512fd885e3
5 changed files with 79 additions and 0 deletions
25
deployment/deploy_to_poweredge.ps1
Normal file
25
deployment/deploy_to_poweredge.ps1
Normal file
|
|
@ -0,0 +1,25 @@
|
||||||
|
# deploy_to_poweredge.ps1
|
||||||
|
|
||||||
|
$remoteHost = "100.76.177.12"
|
||||||
|
$remoteUser = "racer"
|
||||||
|
$remoteDir = "~/picoclaw"
|
||||||
|
|
||||||
|
Write-Host "Creating remote directory..."
|
||||||
|
ssh $remoteUser@$remoteHost "mkdir -p $remoteDir"
|
||||||
|
|
||||||
|
Write-Host "Transferring files..."
|
||||||
|
# Transfer source code (Go files, go.mod, go.sum)
|
||||||
|
scp -r cmd pkg go.mod go.sum $remoteUser@$remoteHost:$remoteDir/
|
||||||
|
|
||||||
|
# Transfer deployment config
|
||||||
|
scp deployment/config.json $remoteUser@$remoteHost:$remoteDir/config.json
|
||||||
|
scp deployment/.env $remoteUser@$remoteHost:$remoteDir/.env
|
||||||
|
scp deployment/picoclaw.service $remoteUser@$remoteHost:$remoteDir/
|
||||||
|
|
||||||
|
Write-Host "Building on remote server..."
|
||||||
|
ssh $remoteUser@$remoteHost "cd $remoteDir && go build -o picoclaw ./cmd/picoclaw/main.go"
|
||||||
|
|
||||||
|
Write-Host "Setting up systemd service..."
|
||||||
|
ssh $remoteUser@$remoteHost "sudo cp $remoteDir/picoclaw.service /etc/systemd/system/ && sudo systemctl daemon-reload && sudo systemctl enable picoclaw && sudo systemctl restart picoclaw"
|
||||||
|
|
||||||
|
Write-Host "Deployment complete!"
|
||||||
15
deployment/picoclaw.service
Normal file
15
deployment/picoclaw.service
Normal file
|
|
@ -0,0 +1,15 @@
|
||||||
|
[Unit]
|
||||||
|
Description=PicoClaw AI Agent
|
||||||
|
After=network.target ollama.service
|
||||||
|
|
||||||
|
[Service]
|
||||||
|
Type=simple
|
||||||
|
User=racer
|
||||||
|
WorkingDirectory=/home/racer/picoclaw
|
||||||
|
ExecStart=/home/racer/picoclaw/picoclaw
|
||||||
|
Restart=always
|
||||||
|
RestartSec=10
|
||||||
|
EnvironmentFile=/home/racer/picoclaw/.env
|
||||||
|
|
||||||
|
[Install]
|
||||||
|
WantedBy=multi-user.target
|
||||||
23
docs/DEPLOY_PLAN.md
Normal file
23
docs/DEPLOY_PLAN.md
Normal file
|
|
@ -0,0 +1,23 @@
|
||||||
|
# Plan - PicoClaw Deployment to PowerEdge
|
||||||
|
|
||||||
|
## Phase 1: Configuration & Preparation
|
||||||
|
- [ ] Create `deployment/config.json` with Ollama and Telegram settings.
|
||||||
|
- [ ] Create `deployment/.env` with the Telegram bot token.
|
||||||
|
- [ ] Prepare a deployment script `deploy.ps1` to handle the transfer.
|
||||||
|
|
||||||
|
## Phase 2: Remote Setup (via SSH)
|
||||||
|
- [ ] Create `~/picoclaw` directory on remote.
|
||||||
|
- [ ] Transfer source code or binary (Build on remote is safer if local Go is missing).
|
||||||
|
- [ ] Install dependencies on remote (if any).
|
||||||
|
|
||||||
|
## Phase 3: Service Management
|
||||||
|
- [ ] Create `picoclaw.service` systemd unit file.
|
||||||
|
- [ ] Enable and start the service.
|
||||||
|
- [ ] Verify logs.
|
||||||
|
|
||||||
|
## Constraints
|
||||||
|
- Host: `100.76.177.12`
|
||||||
|
- User: `racer`
|
||||||
|
- Password: `racerop` (Will attempt to use via script or ask user for key setup)
|
||||||
|
- Model: `granite4:latest` (Ollama)
|
||||||
|
- Telegram: Token provided, User ID: `1826635534`
|
||||||
15
docs/PLAN.md
Normal file
15
docs/PLAN.md
Normal file
|
|
@ -0,0 +1,15 @@
|
||||||
|
# Plan - Update Model to Kimi-K2.5 via Ollama
|
||||||
|
|
||||||
|
## Phase 1: Planning
|
||||||
|
- [x] Analyze user request: Change model to `kimi-k2.5:cloud` via Ollama provider.
|
||||||
|
- [ ] Create/Update configuration file.
|
||||||
|
|
||||||
|
## Phase 2: Implementation (After Approval)
|
||||||
|
- [ ] **DevOps**: Update `deployment/config.json` with `model: kimi-k2.5:cloud`.
|
||||||
|
- [ ] **DevOps**: Transfer `config.json` to `100.76.177.12`.
|
||||||
|
- [ ] **DevOps**: Move `config.json` to `~/.picoclaw/config.json`.
|
||||||
|
- [ ] **DevOps**: Restart `picoclaw.service`.
|
||||||
|
- [ ] **Test**: Check `journalctl -u picoclaw` to verify the model change in the logs.
|
||||||
|
|
||||||
|
## Verification
|
||||||
|
- [ ] Confirm bot responds using the new model.
|
||||||
1
telemetry-id
Normal file
1
telemetry-id
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
5fa8afaf-28a3-45d2-bd70-e6a137ed31ee
|
||||||
Loading…
Add table
Reference in a new issue