Use cargo workspaces (#37)

* Switch to Cargo workspaces

Breaking things into "client", "server" and "common" makes managing the
codebase much easier!

client - anything running on a user's machine for adding history
server - handles storing/syncing history and running a HTTP server
common - request/response API definitions, common utils, etc

* Update dockerfile

1 files changed, 0 insertions, 23 deletions

diff --git a/src/server/mod.rs b/src/server/mod.rs
deleted file mode 100644
index d5e083df..00000000
--- a/src/server/mod.rs
+++ /dev/null
@@ -1,23 +0,0 @@
-use std::net::IpAddr;
-
-use eyre::Result;
-
-use crate::settings::Settings;
-
-pub mod auth;
-pub mod database;
-pub mod handlers;
-pub mod models;
-pub mod router;
-
-pub async fn launch(settings: &Settings, host: String, port: u16) -> Result<()> {
-    // routes to run:
-    // index, register, add_history, login, get_user, sync_count, sync_list
-    let host = host.parse::<IpAddr>()?;
-
-    let r = router::router(settings).await?;
-
-    warp::serve(r).run((host, port)).await;
-
-    Ok(())
-}