web: document how initial query works (fixes #314)
This commit is contained in:
parent
739c8dc4cc
commit
46767406ed
@ -78,10 +78,14 @@ Note there is no built-in access control, so you will need to hide
|
|||||||
hledger-web behind an authenticating proxy (such as apache or nginx)
|
hledger-web behind an authenticating proxy (such as apache or nginx)
|
||||||
if you want to restrict who can see and add entries to your journal.
|
if you want to restrict who can see and add entries to your journal.
|
||||||
|
|
||||||
With journal and timeclock files (but not CSV files, currently)
|
Command-line options and arguments may be used to set an initial
|
||||||
the web app detects changes and will show the new data on the next request.
|
filter on the data. This is not shown in the web UI, but it will be
|
||||||
If a change makes the file unparseable, hledger-web will show an error
|
applied in addition to any search query entered there.
|
||||||
until the file has been fixed.
|
|
||||||
|
With journal and timeclock files (but not CSV files, currently) the
|
||||||
|
web app detects changes made by other means and will show the new data
|
||||||
|
on the next request. If a change makes the file unparseable,
|
||||||
|
hledger-web will show an error until the file has been fixed.
|
||||||
|
|
||||||
---
|
---
|
||||||
# disabled
|
# disabled
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user