| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
* enable tracing on server
* fmt
* instrument handlers
|
| |
|
|
|
|
|
|
|
|
|
| |
* Use the count cache
By default read from the count cache - if there is no value there, then
do a full COUNT. The cache will be filled when the user posts up some
more history
* clean up server db error handling
Co-authored-by: Conrad Ludgate <conrad.ludgate@truelayer.com>
|
| | |
|
| |
|
|
|
| |
* make everything a cow
* fmt + clippy
|
| |
|
|
|
|
|
|
|
|
|
| |
* cleanup reply types
* cleanup error api
* small update
* improve api some more
* fmt
|
|
|
* Switch to Cargo workspaces
Breaking things into "client", "server" and "common" makes managing the
codebase much easier!
client - anything running on a user's machine for adding history
server - handles storing/syncing history and running a HTTP server
common - request/response API definitions, common utils, etc
* Update dockerfile
|
