Remove the HTML client, and expose a JSON API.

This API structure fell out of a conversation with Kit. Described loosely:

	kit: ok
	kit: Here's what I'm picturing in a client
	kit: list channels, make-new-channel, zero to one active channels, post-to-active.
	kit: login/sign-up, logout

	owen: you will likely also want "am I logged in" here

	kit: sure, whoami

1 files changed, 2 insertions, 2 deletions

diff --git a/src/cli.rs b/src/cli.rs
index cc49001..9d0606d 100644
--- a/src/cli.rs
+++ b/src/cli.rs
@@ -6,7 +6,7 @@ use clap::Parser;
 use sqlx::sqlite::{SqliteConnectOptions, SqlitePool, SqlitePoolOptions};
 use tokio::net;
 
-use crate::{app::App, channel, clock, events, index, login};
+use crate::{app::App, channel, clock, events, login};
 
 pub type Result<T> = std::result::Result<T, Error>;
 
@@ -66,7 +66,7 @@ impl Args {
 fn routers() -> Router<App> {
     [channel::router(), events::router(), login::router()]
         .into_iter()
-        .fold(index::routes::router(), Router::merge)
+        .fold(Router::default(), Router::merge)
 }
 
 fn started_msg(listener: &net::TcpListener) -> io::Result<String> {