DIBBS BreakdownDIBBS solicitation → product definition package

Settings

Runtime knobs are stored in the database; secrets and paths live in .env (and override these).

Current configuration

Public URL
https://pdf.rlmconnalllc.com
App root
/home/xfinityr/bd
Data directory
/home/xfinityr/bd/data
Output directory
/home/xfinityr/bd/output
Cache directory
/home/xfinityr/bd/cache
Sign-in required
no
Search provider
ddg (no key — DuckDuckGo HTML)
Contact lookup
on
SMTP
not configured — drafts only (localhost:587)
Cron token
set

Operator / audit stamp

Acting as unattended — unattended. Every build, rebuild, research run and send is stamped with this name in the record and the activity trail.

App sign-inoff
Apache user (REMOTE_USER)not passed through
Command line / cronstamped as the OS account, or BREAKDOWN_OPERATOR=name if set
No sign-in page and no Apache user: builds are stamped unattended. Enable directory privacy above (REMOTE_USER is then picked up automatically, no REQUIRE_AUTH=1 needed) or set BREAKDOWN_OPERATOR on the cron jobs.

Directory privacy (Apache login in front of the app)

active 3 user(s) in /home/xfinityr/bd/.htpasswd

The browser prompt is served by Apache before the request reaches the app. Turn the in-app login off with REQUIRE_AUTH=0 so operators do not sign in twice, and keep CRON_TOKEN set for the /cron endpoints.

Manual actions

Run from a browser while signed in, or from cPanel cron with ?token=… — https://pdf.rlmconnalllc.com/cron/queue?token=YOUR_TOKEN and https://pdf.rlmconnalllc.com/cron/scan?token=YOUR_TOKEN&limit=5.

Drain the job queue Scan the DIBBS index for watched FSCs