e9ff1280d7
The .hledger-web_client_session_key.aes file written at startup is cluttersome and means hledger-web can only be started from a writable directory. What do we lose if I disable it ? https://hackage.haskell.org/package/yesod-core-1.4.33/docs/Yesod-Core.html#v:makeSessionBackend says "Default: Uses clientsession with a 2 hour timeout." http://hackage.haskell.org/package/clientsession-0.9.1.2 says "Securely store session data in a client-side cookie." I think: hledger-web saves (eg) the state of the sidebar as session data, in a cookie, and my web browser saves that locally. And this still seems to work, across server restarts. So what's the purpose of saving this "client session" file on the server ? Let's disable it and find out. |
||
|---|---|---|
| .. | ||
| app | ||
| config | ||
| deploy | ||
| Handler | ||
| Hledger | ||
| messages | ||
| Settings | ||
| static | ||
| templates | ||
| tests | ||
| .ghci | ||
| Application.hs | ||
| CHANGES | ||
| devel.hs | ||
| Foundation.hs | ||
| hledger-web.1 | ||
| hledger-web.cabal | ||
| hledger-web.info | ||
| hledger-web.m4.md | ||
| hledger-web.txt | ||
| Import.hs | ||
| LICENSE | ||
| package.yaml | ||
| README | ||
| Settings.hs | ||
| Setup.hs | ||
A basic web UI for hledger data. Intended to be robust and somewhat useful.