| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
I'd like to tidy up the root a little, and it's nice to have all the
rust crates in one place
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add change-password command & support on server
* Add a test for password change
* review: run format
---------
Co-authored-by: Ellie Huxtable <ellie@elliehuxtable.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* refactor server to allow pluggable db and tracing
* clean up
* fix descriptions
* remove dependencies
|
| |
|
|
|
| |
improve login password incorrect error message
update docs for registration with passwords
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added DELETE register endpoint
* Added remove function to database
* Added unregister to client
* Updated docs
* Renamed functions
* Reformatting
* Used execute instead of fetch in delete_user
|
| |
|
|
|
|
|
|
|
| |
* chore: uuhhhhhh crypto lol
* remove dead code
* fix key decoding
* use inplace encryption
|
| |
|
|
| |
I find it super motivating when people use my stuff, so this makes it
_even easier_ to know when someone new signs up!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
* add some error messages
* fmt
|
| |
|
|
|
|
|
| |
* ignore JB IDEs
* tidy-up imports
* add rustfmt config
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Bump uuid from 0.8.2 to 1.0.0
Bumps [uuid](https://github.com/uuid-rs/uuid) from 0.8.2 to 1.0.0.
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](https://github.com/uuid-rs/uuid/compare/0.8.2...1.0.0)
---
updated-dependencies:
- dependency-name: uuid
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
* patch
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Conrad Ludgate <conrad.ludgate@truelayer.com>
|
| | |
|
| |
|
|
|
|
|
| |
* 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
|
