How can I tell my application about a base path?
In some environments, your application may be running in a subdirectory of your web root. For example:
var/ |- www/ | |- wordpress/ | |- expressive/ | | |- public/ | | | |- index.php
/var/www is the web root, and your Expressive application is in the
expressive/ subdirectory. How can you make your application work correctly in
.htaccess in the application root.
If you are using Apache, your first step is to add an
.htaccess file to your
application root, with directives for rewriting to the
RewriteEngine On RewriteRule (.*) ./public/$1
Using other web servers
If you are using a web-server other than Apache, and know how to do a similar rewrite, we'd love to know! Please submit ideas/instructions to our issue tracker!
Use middleware to rewrite the path
The above step ensures that clients can hit the website. Now we need to ensure that the application can route to middleware!
To do this, we will add pipeline middleware to intercept the request, and rewrite the URL accordingly.
At the time of writing, we have two suggestions:
- los/basepath provides the basic mechanics of rewriting the URL.
- mtymek/blast-base-url provides the URL rewriting mechanics, as well as utilities for generating URIs that retain the base path.
los/basepath, install it via Composer, copy the configuration files to
your application, and then edit the configuration.
To install and copy the configuration:
$ composer require los/basepath $ cp vendor/los/basepath/config/los-basepath.global.php.dist config/autoload/los-basepath.global.php
We recommend copying the global configuration to a local configuration file as well; this allows you to have the production settings in your global configuration, and development settings in a local configuration (which is excluded from git by default):
$ cp config/autoload/los-basepath.global.php config/autoload/los-basepath.local.php
Then edit one or both, to change the
return [ 'los_basepath' => '<base path here>', /* ... */ ];
The base path should be the portion of the web root leading up to the
index.php of your application. In the above example, this would be
mtymek/blast-base-url, install it via Composer, and register some
To install it:
$ composer require mtymek/blast-base-url
If you are using
zend-component-installer, you will be prompted to configure this package
automatically. If you don't choose to do so, you please refer to
class to see how to wire it manually.
If using programmatic pipelines, pipe the middleware early in your pipeline (before routing):
For configuration-driven pipelines, add an entry in your
'middleware_pipeline' => [ ['middleware' => [Blast\BaseUrl\BaseUrlMiddleware::class], 'priority' => 1000], /* ... */ ],
At this point, the middleware will take care of the rewriting for you. No configuration is necessary, as it does auto-detection of the base path based on the request URI and the operating system path to the application.
The primary advantage of
mtymek/blast-base-url is in its additional features:
- it injects
Zend\Expressive\Helper\UrlHelperwith the base path, allowing you to create relative route-based URLs.
- it provides a new helper,
Blast\BaseUrl\BasePathHelper, which allows you to create URLs relative to the base path; this is particularly useful for assets. If you are using zend-view as your templating engine, this view helper will be available out of the box.
Usage of the
BasePath helper is as follows:
// where $basePathHelper is an instance of Blast\BaseUrl\BasePathHelper // as pulled from your container: echo $basePathHelper('/icons/favicon.ico'); // or, from zend-view's PhpRenderer: echo $this->basePath('/icons/favicon.ico');
Found a mistake or want to contribute to the documentation? Edit this page on GitHub!