Servable: a simple web framework
A tiny, convenient web micro-framework built around htmx, Axum, and Maud. Inspired by the "MASH" stack described here and here.
Features
servable provides abstractions that implement common utilities needed by an http server. \
- response headers and cache-busting utilities
- client device detection (mobile / desktop)
- server-side image optimization (see the
imagefeature below) - ergonomic htmx integration (see
htmx-*features below)
Quick Start
use servable::{ServableRouter, servable::StaticAsset, mime::MimeType};
#[tokio::main]
async fn main() {
let route = ServableRouter::new()
.add_page(
"/hello",
StaticAsset {
bytes: b"Hello, World!",
mime: MimeType::Text,
},
);
// usual axum startup routine
let app = route.into_router();
let listener = tokio::net::TcpListener::bind("0.0.0.0:3000")
.await
.unwrap();
axum::serve(listener, app).await.unwrap();
}
Core Concepts
The Servable trait
The Servable trait is the foundation of this stack.
servable provides implementations for a few common servables:
-
StaticAsset, for static files like CSS, JavaScript, images, or plain bytes:use servable::{StaticAsset, mime::MimeType}; let asset = StaticAsset { bytes: b"body { color: red; }", mime: MimeType::Css, }; -
Redirect, for simple http redirects:use servable::Redirect; let redirect = Redirect::new("/new-location").unwrap(); -
HtmlPage, for dynamically-rendered HTML pagesuse servable::{HtmlPage, PageMetadata}; use maud::html; use std::pin::Pin; let page = HtmlPage::default() .with_meta(PageMetadata { title: "My Page".into(), description: Some("A great page".into()), ..Default::default() }) .with_render(|_page, ctx| { Box::pin(async move { html! { h1 { "Welcome!" } p { "Route: " (ctx.route) } } }) });HtmlPageautomatically generates a<head>and wraps its rendered html in<html><body>.
ServableRouter
A ServableRouter exposes a collection of Servables under different routes. It implements tower's Service trait, and can be easily be converted into an Axum Router. Construct one as follows:
# use servable::{ServableRouter, StaticAsset, mime::MimeType};
# let home_page = StaticAsset { bytes: b"home", mime: MimeType::Html };
# let about_page = StaticAsset { bytes: b"about", mime: MimeType::Html };
# let stylesheet = StaticAsset { bytes: b"css", mime: MimeType::Css };
# let custom_404_page = StaticAsset { bytes: b"404", mime: MimeType::Html };
let route = ServableRouter::new()
.add_page("/", home_page)
.add_page("/about", about_page)
.add_page("/style.css", stylesheet)
.with_404(custom_404_page); // override default 404
Features
-
image: enable image transformation via query parameters. This makestokioa dependency.
When this is enabled, allStaticAssetswith a valid mimetype can take an optionalt=query parameter.
See theTransformerEnumin this crate's documentation for details.When
imageis enabled, the image below...# use servable::{ServableRouter, StaticAsset, mime::MimeType}; let route = ServableRouter::new() .add_page( "/image.png", StaticAsset { bytes: b"fake image data", mime: MimeType::Png, } );...may be accessed as follows:
# Original image GET /image.png # Resize to max 800px on longest side GET /image.png?t=maxdim(800) # Crop to a 400x400 square at the center of the image GET /image.png?t=crop(400,400,c) # Chain transformations and transcode GET /image.png?t=maxdim(800);crop(400,400);format(webp) -
htmx-2.0.8: Include htmx sources in the compiled executable.
Use as follows:# use servable::ServableRouter; # #[cfg(feature = "htmx-2.0.8")] let route = ServableRouter::new() .add_page("/htmx.js", servable::HTMX_2_0_8) .add_page("/htmx-json-enc.js", servable::EXT_JSON_1_19_12);
Caching and cache-busting
Control caching behavior per servable:
use chrono::TimeDelta;
use servable::HtmlPage;
let page = HtmlPage::default()
.with_ttl(Some(TimeDelta::hours(1)))
.with_immutable(false);
Headers are automatically generated:
Cache-Control: public, max-age=3600Cache-Control: immutable, public, max-age=31536000(for immutable assets)