| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
* chore: upgrade to 2024 edition
* ugh unsafe
* format
* nixxxxxxxxxxx why
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* chore: update rust toolchain to 1.85
* nix things
* make clippy happy
I've replaced a bunch of &Option<String> with Option<String>.
They were not in hot loops, so a single clone is really no big deal +
keeps things simpler.
* fmt
|
| |
|
|
|
| |
* feat(health): add health check endpoint at `/healthz`
* feat(health-check): remove invalid health-check from docker compose
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* feat: allow advertising a fake version to clients
The server usually runs unstable Atuin, and is well monitored. But let's
not advertised the unstable version to clients, as they will notify
users there is an update available.
* fix test build
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* add verified column to users table
* add database functions to check if verified, or to verify
* getting there
* verification check
* use base64 urlsafe no pad
* add verification client
* clippy
* correct docs
* fix integration tests
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
P99 is usually <100ms which is excellent, but occasionally has big
spikes to 1000ms. This is only on the record index.
I don't want this to get out of hand. I've ran a few test queries and
they all complete very fast, and are purely index scans.
Hopefully this helps figure out if it's a specific user with tonnes of
stores or something? Otherwise there could be something up with my db.
I should probably also figure out some proper log levels or tracing lol.
|
| | |
|
|
|
I'd like to tidy up the root a little, and it's nice to have all the
rust crates in one place
|
