Download the PHP package peterhorne/elmer without Composer
On this page you can find all versions of the php package peterhorne/elmer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download peterhorne/elmer
More information about peterhorne/elmer
Files in peterhorne/elmer
Package elmer
Short Description A simple and flexible routing library for PHP
License
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package elmer
Elmer 
Weniger, aber besser — Dieter Rams
Elmer is a simple and flexible web routing framework for PHP.
Getting Started
This is all it takes to create an application that says 'Hello, world' when a user navigates their browser to the root of your site.
Methods
We assigned a new route to our application by calling the get method on our application instance. The method refers to the HTTP method and we can respond to any HTTP method by changing the method that we call on our application:
Route Parameters
URIs may contain parameters. A parameter starts with a semicolon and is followed by the type of parameter:
This route will match /users followed by any digit, eg. /users/21.
You may use the following parameters:
You can add custom parameters by modifying the patterns property of your application instance like so:
You may also write your own custom regex inline. Be sure to wrap it in parenthesis so it is counted as a matched section.
Optional Parameters
Parts of a URI can be marked as optional by appending a question mark:
This route will match the request /articles, as well as /articles/2011.
Don't forget to set a default value for optional parameters!
Responses
TODO
Filters
Filters 'wrap' around routes so that you can add additional functionality to your application, such as logging and authentication.
A filter looks like this:
The filter above appends 'Bar' to the response so the final result would be FooBar. The route is passed to the filter, which is responsible for continuing the execution of the application by calling the route closure. This allows code to be run before/after, modify the response, or skip calling the route altogether.
Filters can be used for a range of tasks, such as authentication or logging, the limit is your imagination!
Filters are inspired by middleware for Ruby's Rack and Python's WSGI
Multiple filters
You may use as many filters as you like.
Groups
Groups enable you to apply a filter to a limited subset of routes. To define a group all you need to do is wrap several routes in the following:
Now any filters that are declared within the above group will only be applied to routes declared in that same group.
You may nest groups if you like. Filters apply to sub-groups, but a filter in a sub-group will not be applied to routes in the parent group. For example:
In the above code sample Filter A applies for both routes /foo and /bar. Filter B only applies to the route /foo.
Prefixing routes
You can apply a prefix to a group of routes by passing in the URI prefix as the first parameter of the group decleration.
The above route will match the request GET /user/profile.
