atuin/atuin-server/src/router.rs, branch main

chore: move crates into crates/ dir (#1958)

2024-04-18T15:41:28Z

I'd like to tidy up the root a little, and it's nice to have all the rust crates in one place

feat(server): add me endpoint (#1954)

2024-04-16T14:59:11Z

feat: add `store push --force`

2024-02-02T18:01:09Z

This will 1. Wipe the remote store 2. Upload all of the local store to remote Imagine the scenario where you end up with some mixed keys locally :( You confirm this with ``` atuin store verify ``` You then fix it locally with ``` atuin store purge ``` Ensure that your local changes are reflected remotely with ``` atuin store push --force ``` and then (another PR, coming soon), update all other hosts with ``` atuin store pull --force ```

feat: Add change-password command & support on server (#1615)

2024-01-29T11:17:10Z

* Add change-password command & support on server * Add a test for password change * review: run format --------- Co-authored-by: Ellie Huxtable

chore(deps): update axum (#1637)

2024-01-28T13:33:45Z

feat: rework record sync for improved reliability (#1478)

2024-01-05T17:57:49Z

* feat: rework record sync for improved reliability So, to tell a story 1. We introduced the record sync, intended to be the new algorithm to sync history. 2. On top of this, I added the KV store. This was intended as a simple test of the record sync, and to see if people wanted that sort of functionality 3. History remained syncing via the old means, as while it had issues it worked more-or-less OK. And we are aware of its flaws 4. If KV syncing worked ok, history would be moved across KV syncing ran ok for 6mo or so, so I started to move across history. For several weeks, I ran a local fork of Atuin + the server that synced via records instead. The record store maintained ordering via a linked list, which was a mistake. It performed well in testing, but was really difficult to debug and reason about. So when a few small sync issues occured, they took an extremely long time to debug. This PR is huge, which I regret. It involves replacing the "parent" relationship that records once had (pointing to the previous record) with a simple index (generally referred to as idx). This also means we had to change the recordindex, which referenced "tails". Tails were the last item in the chain. Now that we use an "array" vs linked list, that logic was also replaced. And is much simpler :D Same for the queries that act on this data. ---- This isn't final - we still need to add 1. Proper server/client error handling, which has been lacking for a while 2. The actual history implementation on top This exists in a branch, just without deletions. Won't be much to add that, I just don't want to make this any larger than it already is The _only_ caveat here is that we basically lose data synced via the old record store. This is the KV data from before. It hasn't been deleted or anything, just no longer hooked up. So it's totally possible to write a migration script. I just need to do that. * update .gitignore * use correct endpoint * fix for stores with length of 1 * use create/delete enum for history store * lint, remove unneeded host_id * remove prints * add command to import old history * add enable/disable switch for record sync * add record sync to auto sync * satisfy the almighty clippy * remove file that I did not mean to commit * feedback

chore: remove the teapot response (#1496)

2024-01-03T16:37:27Z

It was fun, but it wasn't as informative as it needs to be I'm leaving the function name though :)

feat: add semver checking to client requests (#1456)

2023-12-20T09:03:04Z

* feat: add semver checking to client requests This enforces that the client and the server run the same major version in order to sync successfully. We're using the `Atuin-Version` http header to transfer this information If the user is not on the same MAJOR, then they will see an error like this > Atuin version mismatch! In order to successfully sync, the client and the server must run the same *major* version > Client: 17.1.0 > Server: 18.1.0 > Error: could not sync records due to version mismatch This change means two things 1. We will now only increment major versions if there is a breaking change for sync 2. We can now add breaking changes to sync, for any version >17.1.0. Clients will fail in a meaningful way. * lint, fmt, etc * only check for client newer than server * Add version header to client too

feat: add metrics server and http metrics (#1394)

2023-11-16T23:18:13Z

* feat: add metrics server and http metrics * setup metrics * update default config * fix tests

Add Kris Nova to X-Clacks-Overhead (#1355)

2023-10-28T20:18:16Z

Rest in peace 😔 https://nivenly.org/memorials/krisnova/