Add README explaining how to run Warrant with SQLite (#92)

* Rearrange/update main README

* Add setup tutorial for running Warrant with SQLite

* Rearrange links in main README

Author: kkajla12

README.md

@@ -3,6 +3,7 @@
 </p>
 <p align="center">
   <a href="https://warrant.dev/">Website</a> |
+  <a href="https://app.warrant.dev/signup">Warrant Cloud</a> |
   <a href="https://docs.warrant.dev/">Docs</a> |
   <a href="https://docs.warrant.dev/objecttypes/get-all-object-types/">API Reference</a>
 </p>
@@ -25,7 +26,6 @@ Warrant allows you to define, store, and manage your product's authorization mod
 ## Features
 
 - A real-time, low latency `check` API to perform access checks in your application at runtime (e.g. _is `user:A editor of tenant:X`?_)
-- A real-time `query` API to query and audit access rules for a given subject or object (e.g. _`which users in tenant:1 have access to object:A?`_)
 - Built-in support for roles & permissions (RBAC) + API endpoints to create and manage custom roles & permissions from your application
 - Built-in support for multi-tenant access control
   - Define roles, permissions, access rules, etc. _per tenant_
@@ -60,6 +60,7 @@ The quickest and easiest way to get started with Warrant is by using the managed
 Warrant Cloud is compatible with the same APIs as this open source version and provides additional functionality like:
 
 - An admin dashboard for quickly managing your authorization model and access rules via an intuitive, easy-to-use UI
+- A real-time `query` API to query and audit access rules for a given subject or object (e.g. _`which users in tenant:1 have access to object:A?`_)
 - Multi-region availability
 - Improved access check latency & throughput for large scale use cases.
 
@@ -71,7 +72,7 @@ To self-host or run Warrant locally, follow one of the guides below (select the
 
 - [MySQL](/migrations/datastore/mysql/README.md)
 - [Postgres](/migrations/datastore/postgres/README.md)
-- SQLite (coming soon) - Upvote [the issue](https://github.com/warrant-dev/warrant/issues/14)
+- [SQLite](/migrations/datastore/sqlite/README.md)
 - To request support for another database, please [open an issue](https://github.com/warrant-dev/warrant/issues/new/choose)!
 
 ## SDKs
@@ -102,7 +103,7 @@ To report a bug you found or request a feature that you'd like, open an issue. I
 
 Contributions from the community are welcome! Just be sure to follow some ground rules:
 
-- Never submit a PR without an issue.
+- Never submit a PR without an associated issue.
 - Issues should mention whether the issue is a bug or a feature.
 - Issues reporting a bug should describe (1) steps to reproduce the bug, (2) what the current behavior is, and (3) what the expected behavior should be.
 - Issues requesting a feature should (1) provide a description of the feature and (2) explain the intended use case for the feature.

migrations/datastore/sqlite/README.md

@@ -0,0 +1,55 @@
+# Running Warrant with SQLite
+
+This guide will cover how to run Warrant with SQLite as the datastore/eventstore. Note that running Warrant with SQLite requires that you build Warrant from source.
+
+## Running the Binary
+
+### Install SQLite
+
+Many operating systems (like MacOS) come with SQLite pre-installed. If you already have SQLite installed, you can skip to the next step. If you don't already have SQLite installed, [install it](https://www.tutorialspoint.com/sqlite/sqlite_installation.htm). Once installed, you should be able to run the following command to print the currently installed version of SQLite:
+
+```bash
+sqlite3 --version
+```
+
+### Install Go
+
+[Install Go](https://go.dev/doc/install).
+
+### Build Warrant From Source
+
+Clone the Warrant repository from GitHub or download and unzip the tarball containing the source code for the [latest Warrant release](https://github.com/warrant-dev/warrant/releases/latest).
+
+```bash
+tar -xvf <name_of_tarball>
+```
+
+Navigate to the `cmd/warrant` directory and run `make dev` to build Warrant. This will create a file called `warrant` that contains the executable.
+
+### Create `warrant.yaml` Configuration
+
+Create a file called `warrant.yaml` in the directory containing the Warrant binary. Add properties to configure SQLite as both the datastore and evenstore for Warrant.
+
+```yaml
+# warrant.yaml
+port: 8000
+logLevel: 0
+enableAccessLog: true
+apiKey: replace_with_api_key
+datastore:
+  sqlite:
+    database: warrant
+    inMemory: true
+eventstore:
+  sqlite:
+    database: warrantEvents
+    inMemory: true
+```
+
+NOTE: By default, SQLite will create a database file for both the database and eventstore. The filenames are configurable using the `database` property under `datastore` and `eventstore`. Specifying the `inMemory` option under `datastore` or `eventstore` will bypass creation of a database file and run the SQLite database completely in memory. When running Warrant with the `inMemory` configuration, **any data in Warrant will be lost once the Warrant process is shutdown/killed**.
+
+### Run the Executable
+
+```bash
+./warrant
+```