zog_web: erlang-based web serving using domain routes
Basic Usage (ultra-quickstart)
zog_webas a rebar dependency
- start your erlang node with
-config myconfigwherein you define
web_port, and your
route_dirs(see hnf for examples).
- Now your webserver is running and serving traffic for the routes
listed in your configs under
A complete application using
zog_web is available at
egad, we need tests.
In no specific order:
- Actual documentation
- How domain routes work
- How path routes work
- How to send a page
- How to stall a page
- How to redirect a page
- How to deal with parameters
- Continual synchronization of features with upcoming zog components
When to use zog_web
zog_web when you need a simple way to expose erlang code
to the Internet as a series of URLs.
zog_web when you want your entire web stack embedded in one application.
zog_web provides a web server, domain routing, and URL routing. When paired
zog_web can automatically provide authentication and
authorization against pre-defined paths.
The zog project is a result of my experience deploying a dozen websites using yaws over the past few years. zog provides everyone with a low latency, scalable, minimal, no-magic web framework that gets out of the way so you can focus on getting your content to users.
zog consists of: zog_web, zog_user, zog_template, and a few applications yet to be named (hint: it'll be zog_). Right now, only zog_web is available, but it's completely usable as an isolated application. The remaining applications are being polished/finished/integrated and should be released soon.
- mochiweb, for providing battle-tested web serving components.
- chicagoboss, from where I stole the idea of path routing and method arguments.
- lfe, for shoving lisp macros into erlang.
- and more!