Remove didkit-http as it is now in its own repo

.gitmodules

@@ -1,15 +0,0 @@
-[submodule "http/tests/di-ed25519-test-suite"]
-	path = http/tests/di-ed25519-test-suite
-	url = https://github.com/w3c-ccg/di-ed25519-test-suite.git
-[submodule "http/tests/vc-api-issuer-test-suite"]
-	path = http/tests/vc-api-issuer-test-suite
-	url = https://github.com/w3c-ccg/vc-api-issuer-test-suite.git
-[submodule "http/tests/vc-api-verifier-test-suite"]
-	path = http/tests/vc-api-verifier-test-suite
-	url = https://github.com/w3c-ccg/vc-api-verifier-test-suite.git
-[submodule "http/tests/did-key-test-suite"]
-	path = http/tests/did-key-test-suite
-	url = https://github.com/w3c-ccg/did-key-test-suite.git
-[submodule "http/tests/di-eddsa-2022-test-suite"]
-	path = http/tests/di-eddsa-2022-test-suite
-	url = https://github.com/w3c-ccg/di-eddsa-2022-test-suite.git

Cargo.toml

@@ -1,18 +1,7 @@
 [workspace]
-members = [
-  "http",
-  "cli",
-  "lib",
-  "lib/cbindings",
-  "lib/web",
-]
+members = ["cli", "lib", "lib/cbindings", "lib/web"]
 
-default-members = [
-  "http",
-  "cli",
-  "lib",
-  "lib/cbindings",
-]
+default-members = ["http", "cli", "lib", "lib/cbindings"]
 
 # $ cargo release
 [workspace.metadata.release]

README.md

@@ -38,41 +38,15 @@ Build DIDKit using [Cargo][]:
 ```sh
 $ cargo build
 ```
-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.
-
-
-### Container
-
-Both the CLI and HTTP server are containerised and available under
-`ghcr.io/spruceid/didkit-(cli|http)`.
-
-You can use the images like CLIs:
-```bash
-$ docker run ghcr.io/spruceid/didkit-cli:latest --help
-$ docker run --init -p 8080 ghcr.io/spruceid/didkit-http:latest --port 8080
-```
-
-> You can pass JWKs either by sharing a volume with `docker run --volume`, or by passing the JWK directly with `docker run -e JWK=$MY_JWK` or `docker run didkit-http --jwk $MY_JWK`.
-
-#### Build Images
-
-The Dockerfiles rely on having `ssi` in the root of `didkit` (a symbolic link will not work unfortunately).
-
-Then the images can be built with:
-```bash
-$ docker build -f Dockerfile-cli . -t didkit-cli
-$ docker build -f Dockerfile-http . -t didkit-http
-```
-
-And to use them, replace `ghcr.io/spruceid/didkit-(cli|http):latest` with `didkit-(cli|http)`.
+That will give you the DIDKit CLI executable located at
+`target/debug/didkit`. 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.
 
 ## Usage
 
 DIDKit can be used in any of the following ways:
 
 - [CLI](cli/) - `didkit` command-line program
-- [HTTP](http/) - HTTP server (Rust library and CLI program)
+- [HTTP](https://github.com/spruceid/didkit-http/) - HTTP server (Rust library and CLI program)
 - [FFI](lib/FFI.md) - libraries for C, Java, Android, and Dart/Flutter
 
 [Rust]: https://www.rust-lang.org/