| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
whoops
|
| |
|
|
|
|
| |
I use these in development.
|
|
|
|
| |
Required for new revision of IndieAuth.
|
|
|
|
| |
Seems to be useful on its own.
|
|
|
|
|
|
|
| |
When testing things, I don't test TLS verification, that's what
reqwest unit tests should exist for. I test my things, and some of my
things assume some form of TLS. I don't need it to be valid TLS, I
need it to be TLS so I can use the `https://` links in dev.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This documents the onboarding request schema so somebody unwilling or
unable to run JavaScript (why would you subject yourself to this?) is
still able to use Kittybox.
Since JavaScript is used to provide form interactivity and complex
data structures in the onboarding flow, whoever cannot run JS will
have to manually compose the onboarding request, and this will help
them a little.
I just need to remember to update this if the schema ever changes.
|
|
|
|
|
|
|
| |
- Properly catch IndieAuth errors when parsing grant responses
- Use the new `into_query_pairs()` method to serialize the
authorization request into the authorization endpoint URL
- Migrate to `axum::serve` for simplicity in serving the callback hook
|
|
|
|
|
|
| |
`caddy reverse-proxy -r --from https://localhost:8443 --to http://localhost:8080`
can help meet Kittybox's security assumptions in development (and
could be a good way to meet them in production too.)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is a more efficient way of appending to a query string, as it
avoids a needless copy and borrows most things instead. We can't
really avoid copying here, since we'll need to write to the query
string, but we can avoid an extra copy by borrowing most of our way
through.
|
| |
|
|
|
|
|
|
|
|
| |
Flake lock file updates:
• Updated input 'nixpkgs':
'github:nixos/nixpkgs/9f4128e00b0ae8ec65918efeba59db998750ead6' (2024-07-03)
→ 'github:nixos/nixpkgs/9f918d616c5321ad374ae6cb5ea89c9e04bf3e58' (2024-07-31)
|
|
|
|
|
| |
Naersk has been creating problems for me, and crane seems better
maintained.
|
|
|
|
| |
I'm not sure why this is required.
|
|
|
|
|
|
|
| |
I think I managed to not lose any functionality from my dependencies.
sqlparser remains unupgraded, but that's mostly because it is only
used in one example and it's not worth it to upgrade right now.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Since Kittybox router composition is entirely generic, we can move it
into the library.
I feel like I could also split database types into their own crates,
too.
|
| |
|
|
|
|
|
| |
This somehow allowed me to shrink the construction phase of Kittybox
by a huge amount of code.
|
|
|
|
|
| |
Now the database objects can be uniformly created from a URI. They can
also optionally do sanity checks and one-time initialization.
|
|
|
|
|
|
|
|
|
| |
Per clippy suggestion.
While they're behind a reference counter, and thus cloning is cheap,
we can avoid increasing the reference counter by borrowing here.
Also now the code is a bit prettier.
|
| |
|
|
|
|
| |
This makes the interface more consistent and resistant to misuse.
|
|
|
|
|
|
|
|
|
| |
Added fundamental AutoAuth types. This library can now be used to
augment existing authorization and token endpoints with AutoAuth
capabilities.
See https://github.com/sknebel/AutoAuth/blob/master/AutoAuth.md for
the latest spec draft.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Flake lock file updates:
• Updated input 'flake-utils':
'github:numtide/flake-utils/dbabf0ca0c0c4bce6ea5eaf65af5cb694d2082c7' (2023-06-25)
→ 'github:numtide/flake-utils/b1d9ab70662946ef0850d488da1c9019f3a9752a' (2024-03-11)
• Updated input 'naersk':
'github:nix-community/naersk/abca1fb7a6cfdd355231fc220c3d0302dbb4369a' (2023-07-05)
→ 'github:nix-community/naersk/941ce6dc38762a7cfb90b5add223d584feed299b' (2024-06-18)
• Updated input 'nixpkgs':
'github:nixos/nixpkgs/0fbe93c5a7cac99f90b60bdf5f149383daaa615f' (2023-07-02)
→ 'github:nixos/nixpkgs/9f4128e00b0ae8ec65918efeba59db998750ead6' (2024-07-03)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This might allow me to use SQL syntax in Kittybox's private search
interfaces, allowing for queries of incredible specificity while not
allowing to query private data or inject arbitrary SQL.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Warning, untested. But hopefully works!
|
|
|
|
| |
I forgot, teehee~
|
| |
|
| |
|
| |
|
| |
|