ReportLog
Documentation menu

What is where

PathWhatOwner
/srv/reportlog/releases/<id>One directory per deploy (<UTC time>-<commit>)root, read-only to the app
/srv/reportlog/current→ the release that is runningroot
/srv/reportlog/previous→ the release that ran before it (where rollback goes)root
/srv/reportlog/followThe branch the Updates screen last installed fromroot
/srv/reportlog/repo.gitA mirror of the repository, fetched on deployroot
/etc/reportlog/reportlog.envThe application's settings (see .env.example)root:reportlog, 0640
/etc/reportlog/deploy.envWhere code comes from; the ACME emailroot
/var/lib/reportlogThe application's state (backup.json for the doctor)reportlog, 0750
/var/backups/reportlogLocal database dumpsreportlog, 0700
/usr/local/lib/reportlogThe copy of the deploy scripts that root runsroot
/usr/local/bin/reportlogThe one commandroot
/opt/bugsink→ Bugsink, if this server runs it (/opt/bugsink-<v>)root
/etc/bugsinkBugsink's settings and its own key (bugsink.env)root:bugsink, 0750
/var/lib/bugsinkBugsink's database (SQLite) and what it receivedbugsink, 0750

Services: reportlog-api (the API, on 127.0.0.1:3000), reportlog-job@<name> (one per scheduled job, started by reportlog-<name>.timer), reportlog-alert@ (emails OPS_ALERT_EMAIL when a job fails), reportlog-update-check (root, daily: is there an update?), reportlog-update-request (root: carries out the Updates screen's Check now and Install, below), caddy and postgresql. With error tracking: bugsink and bugsink-snappea (below).

See this page's source