A ruby toolset to build web pages.

Gibheer 7f0df1746a correct forwarded-for header 4 years ago
lib 7f0df1746a correct forwarded-for header 4 years ago
spec 7f0df1746a correct forwarded-for header 4 years ago
.gitignore 8e5268079c don't commit sample apps 5 years ago
.rspec 1de40f7877 added rspec for testing and a thor task 5 years ago
.travis.yml 5b16243973 travis does not know about rbx-head anymore 4 years ago
Gemfile 3876754ab4 update dependencies 4 years ago
Gemfile.lock 3876754ab4 update dependencies 4 years ago
Guardfile 029781bbda guard should now be able to find the correct specs 5 years ago
LICENSE e437deee34 added LICENSE and release new version 5 years ago
README.md b0954de7dc added travis build status 5 years ago
Thorfile 1de40f7877 added rspec for testing and a thor task 5 years ago
zero.gemspec d92dea4695 drop 1.8 support and add 2.0 4 years ago


zero - a toolkit for web services

Build Status

The focus of this project is to provide small helpers for building web services without the need of learning a complete new web stack from the bottom to the top.

As this project is still at the beginning, some things may change or may not be as good as other parts. But we are working on these parts to make them easier to use and stable enough.

The following is a small list of things, the project already provides and at the end you can find a small sample on what is already possible.

parts of the toolkit


A new request implementation is provided to make it easier for accessing all the various elements of a request. It provides an interface for all access headers through the method #access. It also provides a method #params, which returns an object with parameters seperated between query and payload parameters.


A new response is also provided. which is just some lines of code at the moment, but will grow in functionality. We aim at a response which will take care of all the http specific stuff itself, to make it easier for you.


A small router with variables is also provided. It can take static urls, but also dynamic routes and push them to the appropiate controller. It is very lightweight and can therefore be used in other projects, where a Rack::Router is needed but can't do as much and other implementations are just to big.


This part should do the work for you to decide, which template to use. You can define a template directory and a mapping of simple shortcuts of types to all types the template should be rendered with. With these two information the renderer will take care of selecting the correct template, so that you can concentrate on the hard parts.


This is in a very rough state at the moment, but already shows the potential in which direction this hole project should go. It defines a very simple interface for your own controllers, in that it only wants #render to be implemented, but also calls #process to seperate the processing and rendering. It uses the Zero tools at the moment, but later should be able to use other libs too.


To give you an impression on what these parts can already do for you, you can take a look at the sample application here and try it out. It does not take much.