Uptime Kuma has no REST API for monitor data; connect over the same Socket.IO session the web UI uses (login, then read monitorList and heartbeat events) so connected monitors now surface as Resources. Switches the integration's credentials from an API key to username/password, matching what Uptime Kuma's session login expects.
37 lines
932 B
JSON
37 lines
932 B
JSON
{
|
|
"name": "archnest-backend",
|
|
"private": true,
|
|
"version": "0.0.0",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "tsx watch src/server.ts",
|
|
"build": "tsc -b",
|
|
"start": "node dist/server.js"
|
|
},
|
|
"dependencies": {
|
|
"@aws-sdk/client-ec2": "^3.1072.0",
|
|
"@aws-sdk/client-sts": "^3.1072.0",
|
|
"@fastify/cors": "^10.0.1",
|
|
"@fastify/jwt": "^10.1.0",
|
|
"@fastify/multipart": "^10.0.0",
|
|
"@fastify/websocket": "^11.2.0",
|
|
"@types/ssh2": "^1.15.5",
|
|
"bcryptjs": "^2.4.3",
|
|
"better-sqlite3": "^11.8.1",
|
|
"dotenv": "^16.6.1",
|
|
"fastify": "^5.2.1",
|
|
"guacamole-lite": "^1.2.0",
|
|
"node-pty": "^1.1.0",
|
|
"socket.io-client": "^4.8.3",
|
|
"ssh2": "^1.17.0",
|
|
"undici": "^8.5.0",
|
|
"zod": "^3.24.1"
|
|
},
|
|
"devDependencies": {
|
|
"@types/bcryptjs": "^2.4.6",
|
|
"@types/better-sqlite3": "^7.6.12",
|
|
"@types/node": "^22.10.5",
|
|
"tsx": "^4.19.2",
|
|
"typescript": "^5.7.3"
|
|
}
|
|
}
|