Download the PHP package uk/routing without Composer
On this page you can find all versions of the php package uk/routing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 routing
UK.Routing
Simple URL routing library.
Installation
Install it via composer!
or include it inside you're composer.json
Preparing the web server
For Router usage you need to tell the web server, that it should rewrite requests to not existing URL paths to the handling PHP script.
You can do it by 2 different ways:
- Passing the not existing URL path as
GETvariable with specific name, to the script - Passing the not existing URL path VIA
$_SERVER[ 'REQUEST_URI' ](best choice)
Apache web server
For apache its really simple to handle the rewrites.
Create an file with the name .htaccess and put it to the folder where the rewriting should work.
But remember!
.htaccess (distributed configuration files) should only be used if you do'nt have access to the server configuration files.
.htaccess usage comes with some overhead which can be avoided.
But if you admit an server, there is no need to shown you more. You have to know it :-)
The contents of this file depends to the Router type that should be used.
As GET variable (RouterType::REWRITE_TO_GET)
The first line enables the rewrite engine. Second line declares the condition that matches all not existing file calls and the third line matches all not existing directory calls.
The last line rewrites the matching calls to not existing files and directories to index.php and passes the called,
not existing URL path to the theURL GET variable
As 'REQUEST_URI' value (RouterType::REWRITE_TO_REQUEST_URI)
The first line enables the rewrite engine. Second line declares the condition that matches all not existing file calls and the third line matches all not existing directory calls.
The last line rewrites the matching calls to not existing files and directories to index.php and the called. not
existing URL path is passed to $_SERVER[ 'REQUEST_URI' ]
On errors
If the .htaccess usage triggers some server errors (e.g. error 50* or something else) you have to check:
- if apache is enabled to use .htaccess files
- if apache is enabled to use rewriting by .htaccess files (Rights for .htaccess stuff)
- if apache is enabled to use the mod_rewrite extension
The first 2 things can be handled by ensure the AllowOverwrite directive. For details see: Apache HTTP Server Tutorial: .htaccess files
To check if mod rewrite is enable call this inside you're console
If already enabled it outputs: Module rewrite already enabled
If not enabled, the rewrite module gets enabled.
If you not have access to call a console at the server contact the admin or provider and ask him if mod_rewrite is enable for you. If not tell him to enable the mod_rewrite usage via .htaccess
NGINX web server
This is a big TODO! :-)
but i think if you use:
…it should work to get the called URL path via $_SERVER[ 'REQUEST_URI' ] inside index.php
Usage
After defining you're routes you only should call execute() and the routes will be executed.
