What is where
| Path | What | Owner |
|---|---|---|
/srv/reportlog/releases/<id> | One directory per deploy (<UTC time>-<commit>) | root, read-only to the app |
/srv/reportlog/current | → the release that is running | root |
/srv/reportlog/previous | → the release that ran before it (where rollback goes) | root |
/srv/reportlog/follow | The branch the Updates screen last installed from | root |
/srv/reportlog/repo.git | A mirror of the repository, fetched on deploy | root |
/etc/reportlog/reportlog.env | The application's settings (see .env.example) | root:reportlog, 0640 |
/etc/reportlog/deploy.env | Where code comes from; the ACME email | root |
/var/lib/reportlog | The application's state (backup.json for the doctor) | reportlog, 0750 |
/var/backups/reportlog | Local database dumps | reportlog, 0700 |
/usr/local/lib/reportlog | The copy of the deploy scripts that root runs | root |
/usr/local/bin/reportlog | The one command | root |
/opt/bugsink | → Bugsink, if this server runs it (/opt/bugsink-<v>) | root |
/etc/bugsink | Bugsink's settings and its own key (bugsink.env) | root:bugsink, 0750 |
/var/lib/bugsink | Bugsink's database (SQLite) and what it received | bugsink, 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).