Deploi Ops

Deploi Ops — Server Management & Deployment

When this skill is invoked, display this banner:

    ◇
   ◇ ◇        ____             _       _
  ◇   ◇      |  _ \  ___ _ __ | | ___ (_)
 ◇     ◇     | | | |/ _ \ '_ \| |/ _ \| |
  ◇   ◇      | |_| |  __/ |_) | | (_) | |
   ◇ ◇       |____/ \___| .__/|_|\___/|_|
    ◇                    |_|
  ◇ ◇        Ops — Deploy & Manage
 ◇   ◇       deploi.no
  ◇ ◇

This skill handles everything after server creation: deploying apps, domains & DNS, SSL/HTTPS, firewalls, monitoring, databases, and all server administration on Deploi VPS.

Prerequisites:

• .env with DEPLOI_USERNAME and DEPLOI_ACCOUNT_PASSWORD (Deploi account login)
• deploi-servers.json for server access (IP, username, per-server sudo password)

If .env is missing, refer user to deploi-server skill or kundepanel.deploi.no. If deploi-servers.json is missing, the user needs to create a server first via the deploi-server skill.

Credentials source:

• API auth: .env → DEPLOI_USERNAME + DEPLOI_ACCOUNT_PASSWORD
• Server sudo password: deploi-servers.json → per-server password field (NOT .env)

API Foundations

Endpoint: https://api.deploi.no — all commands use HTTP POST requests with a JSON body.

Node.js API Helper

node -e "
const https = require('https');
const data = JSON.stringify(<PAYLOAD>);
const req = https.request('https://api.deploi.no', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json', 'Content-Length': Buffer.byteLength(data) }
}, (res) => {
  let body = '';
  res.on('data', c => body += c);
  res.on('end', () => console.log(body));
});
req.write(data);
req.end();
"

Authentication

Read DEPLOI_USERNAME and DEPLOI_ACCOUNT_PASSWORD from .env, then:

{ "command": "Login", "username": "<email>", "password": "<password>" }

Extract data.token and data.clients[0].id from the response. Use these for all authenticated calls.

If any API call returns messageId: 41 ("Not logged in"), the token has expired — re-authenticate.

Complete API Command Reference

Routing: What Do You Need?

Based on the user's request, load the appropriate reference:

For server operations (restart, CPU monitoring, status checks, upgrade), see below.

Server Operations via API

Server Status Check

{ "command": "GetServerInfo", "token": "<t>", "id": "<server-id>" }

Returns serverInfo.virtual.mainip, RAM, CPU, status, and more.

Note: Servers with status: "off" return success: false. GetServers still lists them.

RestartVirtualServer

{ "command": "RestartVirtualServer", "token": "<t>", "id": "<server-id>" }

Get server-id from GetServers (the id field, not the name).

After restart: Wait 30–60 seconds, then verify with GetServerInfo that status is "active".

Upgrade/Downgrade Server

{ "command": "UpdateVirtualServer", "token": "<t>", "id": "<server-id>", "setCpu": true, "cpucent": cpucents, "setRam": false, "ram": gbram, "diskChange": [{"id": "<disk id>", "size": gbsize } ]}

Get server-id from GetServers (the id field, not the name).

After upgrade/downgrade: Wait 30–90 seconds, then verify with GetServerInfo that running is true.

Logout

{ "command": "Logout", "token": "<t>" }

Decision Frameworks

When to Create a New Server

Server Conventions

All Deploi VPS servers follow these conventions:

• Username: cursor
• Auth: SSH key (~/.ssh/id_ed25519) — password login disabled
• Sudo password: Per-server, stored in deploi-servers.json
• OS: Ubuntu 24.04 (default)
• App directory: /home/cursor/apps/<app-name>/
• Backups: /home/cursor/backups/

To connect: ssh <server-name> (uses the SSH config alias)

Important Notes

• Always ask before making changes that affect running services
• Back up configs before modifying them (cp nginx.conf nginx.conf.bak)
• Test configs before reloading (nginx -t before systemctl reload nginx)
• Sudo password comes from deploi-servers.json — NOT from .env
• No server deletion via API — users must use kundepanel.deploi.no
• curl is blocked by the API — all API calls must use the Node.js helper pattern
• clientid is a number — wrong clientid returns "Not logged in" (messageId 41)
• Duplicate server names are allowed — always check GetServers before creating

API Error Reference