Getting Started - Automatic Installation


The NeverBlock Phar Installer is a tool that assists in the installation of the NeverBlock PHP (version 3.0 ) solution. This can be done instead of the steps covered in Manual Installation. It will install the files in the specified directory, or a default nb directory. Some of the configuration will be handled by the installer, regarding file renaming and identification keys.


The latest version can be downloaded using the following link.

Latest Version (Neverblock version 3.11)

Execute the installer

Run the installer

Once the phar has been downloaded, place it in the directory where you want the NeverBlock files kept. When running the installer you can specify the path you wish to install the files, or let it run as default. There is also an optional parameter to define the logfile used, the purpose of which is described in the Configuration - Logfile section.

# Create and install files under default 'nb' directory 

Optional parameters:

# Create and install files under the specific directory
./neverBlockInstaller.phar --path=specific/path 

# Install files into current directory
./neverBlockInstaller.phar --path=.

# Path to logfile
./neverBlockInstaller.phar --logfile=path/logfile

# Path to writable_path (In case of no xcache or apc installed.)
./neverBlockInstaller.phar --writable_path=path/writable_path

Analysing the response

Once executed we will be presented with a response similar to what can be seen below. We can analyse this in two separate sections, the diagnostic results, and the required scripts.


Diagnosis results

Once the phar has been run it will show you the results of some tests of the configuration. Note that the IP detection will require the diag.php to be run manually. For more details regarding these results and running manually see sections Run the diag.php and Possible diag.php results.

Required scripts

Below the diagnosis results we see two scripts, the names of which have been automatically generated. These scripts show us the names of our frontend_loader.js and backend_loader.php, and will be the paths to use when Displaying Ads.