Support

One person makes both apps. Email gets read, and a report with a log attached gets fixed faster.

Getting in touch

Sending a useful report for Pharos

Pharos writes a log for every task it runs, and can bundle them for you: Activity, then Export Logs. The bundle contains the per-task logs, a redacted copy of your configuration, and system information, with a README explaining what is in it.

It is redacted before it is written. Credentials are stripped from repository URLs, environment variables and access keys, so the bundle can be sent without handing over the keys to your backups. If you would like to check, everything in it is plain text.

For a single failure, the error inspector has a copy button that does the same scrubbing on one message.

Sending a useful report for Denarius

The ledger itself is the best evidence, and usually the last thing you should send. Instead:

Run git log --oneline inside your ledger bundle and include the last few lines. Every action Denarius took is recorded there in plain English, so it usually shows exactly what happened without exposing any figures.

If the problem is a file Denarius will not read, a minimal journal that reproduces it is worth more than the real one. Three transactions that fail is a better bug report than three years of books that mostly work.

Questions that come up

Before you write

Check the changelog first. If the thing you hit was fixed in a release you have not installed yet, that is the fastest answer either of us will get.