Guides

Integration guides

Nanoesis runs anywhere Node runs, and stores files in anything with get, put, and delete. Pick your stack for a step-by-step setup. New to how it fits together? Start with Getting started.

Every guide follows the same three moves: give nanoesis a Storage for your files, wire it with createEditor, and serve two routes. Only the storage and the host change between them.

Node or any server

The fastest way to see nanoesis running: two folders on disk and a small Node server. The same shape is the starting point for every cloud host.

Azure Functions and Blob Storage

The stack this site runs on: Azure Functions for the editor and Blob Storage for files, with the built site served straight from a $web container. Ready-made adapters mean almost no code of your own.

AWS Lambda and S3

There is no ready-made AWS adapter, but a Storage is only three methods. Implement it over an S3 bucket, then host the editor on Lambda, Fargate, or any Node server.

Google Cloud Run and Cloud Storage

No ready-made Google Cloud adapter, but a Storage is three methods. Implement it over a Cloud Storage bucket and host the editor on Cloud Run.

Once it is running, open it in a browser, create a page, and press Publish. Your built static site lands in whatever storage you set as the website. For how published files are cached, and the one knob you control, see Caching and cache-busting.