| Commit message (Collapse) | Author |
|---|
|
The data part of the add history request is actually a string. I don't
want to introduce any structure here, and would rather keep it as "just
a blob". Even if that blob has structure secretly!
My fault for missing this in the last review
|
|
* make everything a cow
* fmt + clippy
|
|
Also:
- Ensures that a key is generated as soon as a user registers!
- Ensures that "atuin key" will generate a key if needed, and doesn't
double base64 encode data
And a few other little fixes :)
Resolves #85
Resolves #86
|
|
|
|
* fix some bugs
* format
|
|
* initial importer trait
* appease linters
* improve file handling. fixes #66
* use size hint
* format + comment
* update serde rename mess
* tested :sunglasses: :rocket:
* small formatting
|
|
|
|
|
|
|
|
* Added resh history importer
* Silence trivial clippy warnings for the PR CI
|
|
* Improve readme
* Add demo gif
* Update readme
* Add mac build
* Amend release config
* Update gif
|
|
|
|
|
|
* Begin moving to sqlx for local too
* Stupid scanners should just have a nice cup of tea
Random internet shit searching for /.env or whatever
* Remove diesel and rusqlite fully
|
|
Also allow unique listing and more ergonomic cwd usage
|
|
* 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
|
