README issues that trip up anyone setting PULSE up or trying to use workflows:
"Workflow Creation (Future Feature)" – workflows, prompts, routes, params, dry-run and the Scheduler all exist but are undocumented.
Database schema section lists executions.worker_id/command/output/created_at and workers.last_seen – none exist; real columns are logs, started_at, last_heartbeat, plus the scheduled_commands table which is not mentioned.
Worker setup says to clone the repo to /opt/pulse-worker and run node worker.js, but worker.js lives in worker/, and the repo contains no worker/package.json (the deployed worker on CT153 has its own with axios, node-fetch, ws, dotenv). npm install at repo root will not install axios.
package.json: "main": "index.js", no start script, licence ISC vs README MIT (no LICENSE file).
Env vars HOST, GANDALF_API_KEY, EXECUTION_MAX_MINUTES, NODE_ENV are used but undocumented; no .env.example for server or worker.
Troubleshooting "Commands Stuck in Running – this was fixed" is not accurate (see the stuck-execution issue).
Suggested fix
Commit worker/package.json and .env.example files, add a Workflow Reference section (all step types + fields + a worked example), correct the schema tables, add npm start.
## Overview
README issues that trip up anyone setting PULSE up or trying to use workflows:
- "Workflow Creation (Future Feature)" – workflows, prompts, routes, params, dry-run and the Scheduler all exist but are undocumented.
- Database schema section lists `executions.worker_id/command/output/created_at` and `workers.last_seen` – none exist; real columns are `logs`, `started_at`, `last_heartbeat`, plus the `scheduled_commands` table which is not mentioned.
- Worker setup says to clone the repo to `/opt/pulse-worker` and run `node worker.js`, but `worker.js` lives in `worker/`, and the repo contains no `worker/package.json` (the deployed worker on CT153 has its own with `axios`, `node-fetch`, `ws`, `dotenv`). `npm install` at repo root will not install `axios`.
- `package.json`: `"main": "index.js"`, no `start` script, licence `ISC` vs README `MIT` (no LICENSE file).
- Env vars `HOST`, `GANDALF_API_KEY`, `EXECUTION_MAX_MINUTES`, `NODE_ENV` are used but undocumented; no `.env.example` for server or worker.
- Troubleshooting "Commands Stuck in Running – this was fixed" is not accurate (see the stuck-execution issue).
## Suggested fix
Commit `worker/package.json` and `.env.example` files, add a Workflow Reference section (all step types + fields + a worked example), correct the schema tables, add `npm start`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
README issues that trip up anyone setting PULSE up or trying to use workflows:
executions.worker_id/command/output/created_atandworkers.last_seen– none exist; real columns arelogs,started_at,last_heartbeat, plus thescheduled_commandstable which is not mentioned./opt/pulse-workerand runnode worker.js, butworker.jslives inworker/, and the repo contains noworker/package.json(the deployed worker on CT153 has its own withaxios,node-fetch,ws,dotenv).npm installat repo root will not installaxios.package.json:"main": "index.js", nostartscript, licenceISCvs READMEMIT(no LICENSE file).HOST,GANDALF_API_KEY,EXECUTION_MAX_MINUTES,NODE_ENVare used but undocumented; no.env.examplefor server or worker.Suggested fix
Commit
worker/package.jsonand.env.examplefiles, add a Workflow Reference section (all step types + fields + a worked example), correct the schema tables, addnpm start.