2.1 KiB
2.1 KiB
Deployment
Node Agent
Run this on every Incus host:
cd /opt/incus-backup-ui/backend
cp .env.example .env
npm install
sudo npm start
Important .env values:
PORT=3000
API_TOKEN="long-random-token-at-least-32-characters"
ALLOWED_MANAGEMENT_IPS="management-server-ip"
API_TOKEN is required and must be at least 32 characters long. If ALLOWED_MANAGEMENT_IPS is set, the agent only accepts requests from those comma-separated IP addresses.
Install systemd service:
sudo cp deploy/systemd/incus-backup-agent.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now incus-backup-agent
sudo journalctl -u incus-backup-agent -f
Management API
Run this on the management server:
cd /opt/incus-backup-ui/management
cp .env.example .env
npm install
npm start
Important .env values:
PORT=3100
SESSION_SECRET="long-random-secret"
AUTH_USERNAME="admin"
AUTH_PASSWORD="initial-password"
DATABASE_PATH="./management.sqlite"
CORS_ORIGINS="https://backup.example.com"
SESSION_COOKIE_SECURE=true
ALLOW_INSECURE_AGENT_HTTP=false
AUTH_PASSWORD is required for the first start when the user database is empty. CORS_ORIGINS must list the frontend origins that are allowed to use cookie-authenticated API calls. Agent URLs must use https://; only set ALLOW_INSECURE_AGENT_HTTP=true for local development.
Reset an existing password:
npm run reset-password -- admin "new-password"
Install systemd service:
sudo useradd --system --home /opt/incus-backup-ui --shell /usr/sbin/nologin incus-backup
sudo chown -R incus-backup:incus-backup /opt/incus-backup-ui/management
sudo cp deploy/systemd/incus-backup-management.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now incus-backup-management
sudo journalctl -u incus-backup-management -f
Frontend
Point the frontend at the management API:
cd /opt/incus-backup-ui/frontend
npm install
VITE_API_URL=http://management-server:3100/api npm run build
npm run preview -- --host 0.0.0.0
For production, put the frontend and management API behind HTTPS.