m0

Preview. Write a web application in Mojo on the mojo-http framework: an HTTP/1.1 server, a router and views, HTML fragments for htmx and Datastar, Server-Sent Events, and a host that runs the lot as one binary with no interpreter in it.

This wheel carries the framework's source and a small CLI that builds against it. It is pure Python and installs anywhere; the toolchain it drives runs on macOS arm64 and glibc Linux (x86-64, aarch64).

uvx m0 new shop                   # writes ./shop; needs no toolchain and no network
cd shop && uv sync                # the pair it pinned: m0, and the one exact mojo it is gated on
uv run m0 build                   # src/server.mojo -> bin/server, about ten seconds
uv run m0 test                    # mojo run over test/test_*.mojo, two to four seconds a file
uv run m0 dev -- --port 8080      # build, serve, rebuild on save; the old server serves until a build succeeds
uv run m0 doctor                  # the toolchain checks, then bin/server's own --doctor
uv run m0 image                   # docker build of deploy/Dockerfile, then the image's about.json
uv run m0 include                 # where the framework's source is: read it

Exit codes are a closed set: 0; 1 the tool m0 ran failed; 2 the command line cannot be accepted; 78 m0 refused before running anything, with one m0: detail (fix) line on stderr.

m0 runs the mojo installed in its own environment — never the one on PATH — and refuses a version it was not gated on, naming the pin to add. There is no override: every gate in the repository ran on that one compiler.

m0 is versioned apart from the repository it is cut from, and stays 0.x until an application outside that repository has soaked on it. m0/_build_info.json records the tree.

MIT. The lightbug_http fork inside is MIT too; both licences are in m0/licenses/.