From 08183d3bba6f3aebe7270347ae799f113d7a7a12 Mon Sep 17 00:00:00 2001 From: Brujo Benavides Date: Tue, 1 Dec 2015 16:38:54 -0300 Subject: [PATCH] [#1] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1e79a42..cf254c8 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ Eventually, all applications shared that same *base_handler*, so we decided to a ## Architecture This project dependency tree is a great way to show the architecture behind it. -![Architecture](https://docs.google.com/drawings/d/1mlJTIxd7mH_48hcWmip_zW6rfzglbmSprpGSsfhjcsM/pub?w=367&h=288) + As you'll see below, **Sumo Rest** gives you _base handlers_ that you can use on your **Cowboy** server to manage your **Sumo DB** entities easily. You just need to define your routes using **Trails** and provide proper metadata for each of them. In particular, you need to provide the same basic metadata **Swagger** requires. You can manually use the base handlers and call each of their functions when you need them, but you can also use **Mixer** to just _bring_ their functions to your own handlers easily.