pf_app
Paul Trowbridge
146961cc17
server.js builds its pg pool from DB_HOST/DB_PORT/DB_NAME/DB_USER/ DB_PASSWORD, and that is what install.sh writes, but pf.sh had been written against a DATABASE_URL/PF_USER scheme that nothing consumes. The consequences were real: `status` always reported the database unreachable, and `config` rewrote .env with cat >, replacing a working connection with keys the server ignores. Connect through a run_psql helper built from the DB_* vars, and have config prompt for those six keys instead. Each prompt defaults to the current value so entering through changes nothing, the password prompt is hidden and keeps the stored one when left blank, and any other key already in .env is carried over rather than dropped. PF_USER goes away with it — pf_user reaches the server in the request body, never from the environment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||