slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: ui, web: mention debug output

Browse Source
This commit is contained in:
Simon Michael 2022-11-03 17:16:55 -10:00
parent cc1ea894aa
commit 32d7cb5287
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
hledger-ui/hledger-ui.m4.md
View File

@ -355,6 +355,11 @@ CPU and memory usage can sometimes gradually increase, if `hledger-ui --watch` i
To work around, `q`uit and restart it, To work around, `q`uit and restart it,
or (where supported) suspend (`CTRL-z`) and restart it (`fg`). or (where supported) suspend (`CTRL-z`) and restart it (`fg`).
## Debug output
You can add `--debug[=N]` to the command line to log debug output.
This will be logged to the file `hledger-ui.log` in the current directory.
N ranges from 1 (least output, the default) to 9 (maximum output).
# ENVIRONMENT # ENVIRONMENT

11
hledger-web/hledger-web.m4.md
View File

@ -401,6 +401,17 @@ And here's how to test adding it with curl. This should add a new entry to your
$ curl http://127.0.0.1:5000/add -X PUT -H 'Content-Type: application/json' --data-binary @txn.json $ curl http://127.0.0.1:5000/add -X PUT -H 'Content-Type: application/json' --data-binary @txn.json
``` ```
# DEBUG OUTPUT
## Debug output
You can add `--debug[=N]` to the command line to log debug output.
N ranges from 1 (least output, the default) to 9 (maximum output).
Typically you would start with 1 and increase until you are seeing enough.
Debug output goes to stderr, interleaved with the requests logged on stdout.
To capture debug output in a log file instead, you can usually redirect stderr, eg:\
`hledger-web --debug=3 2>hledger-web.log`.
# ENVIRONMENT # ENVIRONMENT
_LEDGER_FILE_ _LEDGER_FILE_