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

doc: remove mention of hledger-web's edit form

Browse Source 
(cherry picked from commit 77f4d9e4f6a4f66511aa9cbb28be9602f938fd4f)
This commit is contained in:
Simon Michael 2015-01-12 08:02:01 -08:00
parent 414a33f3e4
commit 8b51f986b6
1 changed files with 19 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
doc/manual.md
View File

@ -1408,7 +1408,7 @@ See the package page for more.
[hledger-web](http://hackage.haskell.org/package/hledger-web)
provides a web-based user interface for viewing and modifying your ledger.
It includes an account register view that is more useful than the command-line register, and basic data entry and editing.
It includes an account register view that is more useful than the command-line register, and basic data entry.
You can see it running at [demo.hledger.org](http://demo.hledger.org).
web-specific options:
@ -1435,20 +1435,26 @@ served from a generic web server like apache, which is good at handling static
files and caching. One can also serve the files in a separate domain to reduce
cookies overhead.
The web app detects changes in journal files, showing the new data on the next request.
(It does not currently detect changes in CSV or rules files.)
The web app detects changes in journal files (but not CSV or rules
files, currently), showing the new data on the next request. If such
a change makes the file unparseable, hledger-web will show an error
until the file has been fixed.
**Note:** unlike any other hledger command, `web` can alter existing journal
data, via the edit form. A numbered backup of the file is saved on
each edit, normally (ie if file permissions allow, disk is not full, etc.)
Also, there is no built-in access control. So unless you run it behind an
authenticating proxy, any visitor to your server will be able to see and
overwrite the journal file (and included files.)
Note there is no built-in access control, so unless you run it behind
an authenticating proxy (such as apache or nginx), any visitor to your
server will be able to see and add entries to the journal.
hledger-web disallows edits which would leave the journal file not in
valid [journal format](#journal). If the file becomes unparseable
by other means, hledger-web will show an error until the file has been
fixed.
<!-- edit form -->
<!-- Note: unlike any other hledger command, `web` can alter existing journal -->
<!-- data, via the edit form. A numbered backup of the file is saved on -->
<!-- each edit, normally (ie if file permissions allow, disk is not full, etc.) -->
<!-- Also, there is no built-in access control. So unless you run it behind an -->
<!-- authenticating proxy, any visitor to your server will be able to see and -->
<!-- overwrite the journal file (and included files.) -->
<!-- hledger-web disallows edits which would leave the journal file not in -->
<!-- valid [journal format](#journal). If the file becomes unparseable -->
<!-- by other means, hledger-web will show an error until the file has been -->
<!-- fixed. -->
Examples: