feat(build): add page on hyper nano

src/.vitepress/config.mjs

@@ -59,6 +59,10 @@ export default defineConfig({
             text: '🔐 Securing hyper',
             link: '/docs/build/securing-hyper'
           },
+          {
+            text: '🍷 hyper {nano}',
+            link: '/docs/build/hyper-nano'
+          },
           {
             text: '⨠ Custom Middleware',
             link: '/docs/build/custom-middleware',

src/docs/build/hyper-nano.md

@@ -0,0 +1,89 @@
+# hyper {nano} - hyper in a Bottle
+
+Because hyper is built to be modular using the [Ports and Adapters](/docs/concepts/clean-cloud-architecture) Architecture, **`Adapters` and `Apps` are _interchangeable_**. This is how we can test our business layer without choosing a database, for example. We can simply stub the `Adapter` that implements the `Port` that the core business logic interacts with.
+
+This also means The hyper Service Framework can be ran using a set of `Adapters` designed to run ephemerally, perhaps for development environments. This is where hyper `{nano}` shines.
+
+hyper `{nano}` is a compiled hyper `Server` using a set of "local development" adapters. It uses the HTTP-based RESTful app based on `express`[built by the Core team](/docs/api-reference/rest/index), and the same hyper `Core`, but with a set of adapters that allow it to run locally sandboxed, and is fast and simple to quickly spin up and then blow away.
+
+- data (powered by [In-Memory MongoDB](https://github.com/hyper63/hyper-adapter-mongodb))
+- cache (powered by [Sqlite](https://github.com/hyper63/hyper-adapter-sqlite))
+- storage (powered by your local [file system](https://github.com/hyper63/hyper-adapter-fs))
+- search (powered by [Sqlite and Minisearch](https://github.com/hyper63/hyper-adapter-minisearch))
+- queue (powered by [Sqlite and an in-memory queue](https://github.com/hyper63/hyper-adapter-queue))
+
+hyper `{nano}` is great for development or sandboxed short-lived environments ie. GitHub Workspaces or GitPod. Developers will use hyper `{nano}` to power their services tier in their local development environment.
+
+Then in deployed environments, an hosted hyper `Server` is used that is running `Adapters` backed by more robust external services. **The interactions with the hyper Server do not change!**
+
+To use `hyper nano`, you can download a compiled binary and run it
+
+```sh
+curl https://hyperland.s3.amazonaws.com/hyper -o nano
+chmod +x nano
+./nano
+```
+
+There are binaries built for each major platform:
+
+- [Linux](https://hyperland.s3.amazonaws.com/hyper)
+- [Darwin (Mac)](https://hyperland.s3.amazonaws.com/hyper-x86_64-apple-darwin)
+- [Darwin ARM (Mac M1)](https://hyperland.s3.amazonaws.com/hyper-aarch64-apple-darwin)
+- [Windows](https://hyperland.s3.amazonaws.com/hyper-x86_64-pc-windows-msvc.exe)
+
+### Node Usage
+
+Alternatively, if you use `Node`, you may run `hyper-nano` using `npx`:
+
+```sh
+npx hyper-nano --domain=foobar --experimental --data --cache ...
+```
+
+### Deno Usage
+
+Alternatively, if you use `Deno` you may run `hyper-nano` directly from the source:
+
+```sh
+deno run --allow-run --allow-env --allow-read --allow-write=__hyper__ --allow-net --unstable --no-check=remote https://raw.githubusercontent.com/hyper63/hyper/main/images/nano/mod.js
+```
+
+If you'd like to programmatically start `hyper-nano`, you can import `main.js` and run `main`:
+
+```js
+import { main } from "https://raw.githubusercontent.com/hyper63/hyper/main/images/nano/main.js";
+
+await main();
+```
+
+and then run:
+
+```sh
+deno run --allow-env --allow-read --allow-write=__hyper__ --allow-net --unstable --no-check=remote foo.js
+```
+
+All of these examples above will start a `hyper nano` instance, listening on port `6363`. You can
+then consume your hyper instance
+[`hyper-connect`](https://github.com/hyper63/hyper/tree/main/packages/connect) (recommended) or
+using `HTTP`.
+
+To consume using [`hyper-connect`](https://github.com/hyper63/hyper/tree/main/packages/connect) pass
+`http://127.0.0.1:[port]/[domain]` to `hyper-connect` as your
+[`connection string`](https://docs.hyper.io/app-keys#nq-connection-string)
+
+Consume with [`hyper-connect`](https://github.com/hyper63/hyper/tree/main/packages/connect):
+
+```js
+import { connect } from "hyper-connect";
+
+const hyper = connect("http://127.0.0.1:6363/test");
+
+await hyper.data.list();
+```
+
+Or consume via HTTP
+
+```sh
+curl http://127.0.0.1:6363/data/test
+```
+
+Learn more about hyper `{nano}` [here](https://github.com/hyper63/hyper/tree/main/images/nano)