libssl-dev
, as well as pkg-config
,build-essential
, or equivalent core toolsets if they aren't already installed.cargo install
for the given target package: didkit-cli | didkit-http
.stable
version; be sure to switch the installation defaults to nightly
if the calling application or forked source code does depend on them.didkit
repository in a parallel directory between downloading didkit and building it.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.ghcr.io/spruceid/didkit-(cli|http)
.Note: You can pass JWKs either by sharing a volume withdocker run --volume
, or by passing the JWK directly withdocker run -e JWK=$MY_JWK
ordocker run didkit-http --jwk $MY_JWK
.
didkit
(a symbolic link will not work, unfortunately).ghcr.io/spruceid/didkit-(cli|http):latest
with didkit-(cli|http)
.