Installation
DIDKit can be installed manually or in containerized form.
#
ManualDIDKit is written in Rust. To get Rust, you can use Rustup.
We depend on some Rust nightly features. When installing with Rustup, pick the nightly release channel. Or run rustup default nightly
to switch to it.
(More info)
Spruce's ssi library must be cloned alongside the didkit
repository:
Build DIDKit using Cargo:
That will give you the DIDKit CLI and HTTP server executables located at
target/debug/didkit
and target/debug/didkit-http
, respectively. You can also build and install DIDKit's components separately. Building the FFI libraries will require additional dependencies. See the corresponding readmes linked below for more info.
#
ContainerBoth the CLI and HTTP server are containerised and available under
ghcr.io/spruceid/didkit-(cli|http)
.
The image is private for now, so a Personal Access Token is required. Once created you can login like so:
You can use the images like CLIs:
Note: You can pass JWKs either by sharing a volume with
docker run --volume
, or by passing the JWK directly withdocker run -e JWK=$MY_JWK
ordocker run didkit-http --jwk $MY_JWK
.
#
Build ImagesThe Dockerfiles rely on having ssi in the root of didkit
(a symbolic link will not work, unfortunately).
Then the images can be built with:
And to use them, replace ghcr.io/spruceid/didkit-(cli|http):latest
with didkit-(cli|http)
.