Working with PHP frameworks

ExeOutput for PHP is being developped in order to work with PHP frameworks. Since they generally work with a lot of PHP includes, ExeOutput for PHP will intercept all files requested by the PHP runtime and makes them available (see accessing files in PHP).

If your favorite PHP framework does not work fine, please see the Advice for getting started with PHP applications in ExeOutput for PHP topic. For instance, if PHP displays “missing file” errors and warnings like “php failed to open stream”, you can try to mark files in the File Manager (select your files, click File Properties and turn this option on: Unpack the file(s) to virtual memory at startup).

Redirect directory requests to the router script (homepage)

Some PHP frameworks support pretty URLs, similar to Apache’s mod_rewrite in specific cases.

Be sure to turn on the option to redirect all of these non-files requests to the router index.php script of your framework.

Initial page / Base URL

If your homepage index.php shouldn’t be the first URL to be displayed, you can provide your own URL for application bootstrap: see Application Startup URL.

Base URLs should begin with http://heserver (see Accessing Files in Compiled PHP Applications).

List of PHP frameworks tested and compatible with ExeOutput for PHP

The following PHP frameworks were successfully tested:

  • Laravel: keep the “storage” folder outside the EXE, i.e. in the “Data” subfolder - see Accessing Source Files from PHP.
  • CodeIgniter
  • Fat-free framework (F3)

This is an incomplete list: a missing framework doesn’t mean that your PHP application based on it won’t work once compiled with ExeOutput for PHP.

Accessing Files in Compiled PHP Applications

How compiled PHP applications work


Copyright G.D.G. Software 2017. All Rights Reserved.