Download the PHP package pacificnm/application without Composer
On this page you can find all versions of the php package pacificnm/application. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package application
PacificNM Skeleton Application
Introduction
This is a skeleton application using the PacificNM layer and module systems. This application is meant to be used as a starting place for those looking to get their feet wet with PacificNM.
Installation using Composer
The easiest way to create a new PacificNM project is to use Composer. If you don't have it already installed, then please install as per the documentation.
To create your new PacificNM project:
Once installed, you can test it out immediately using PHP's built-in web server:
This will start the cli-server on port 8080, and bind it to all network interfaces. You can then visit the site at http://localhost:8080/
- which will bring up PacificNM welcome page.
Note: The built-in CLI server is for development only.
Development mode
The skeleton ships with zf-development-mode by default, and provides three aliases for consuming the script it ships with:
You may provide development-only modules and bootstrap-level configuration in
config/development.config.php.dist
, and development-only application
configuration in config/autoload/development.local.php.dist
. Enabling
development mode will copy these files to versions removing the .dist
suffix,
while disabling development mode will remove those copies.
Development mode is automatically enabled as part of the skeleton installation process.
After making changes to one of the above-mentioned .dist
configuration files you will
either need to disable then enable development mode for the changes to take effect,
or manually make matching updates to the .dist
-less copies of those files.
Running Unit Tests
To run the supplied skeleton unit tests, you need to do one of the following:
- During initial project creation, select to install the MVC testing support.
- After initial project creation, install zend-test:
Once testing support is present, you can run the tests using:
If you need to make local modifications for the PHPUnit test setup, copy
phpunit.xml.dist
to phpunit.xml
and edit the new file; the latter has
precedence over the former when running tests, and is ignored by version
control. (If you want to make the modifications permanent, edit the
phpunit.xml.dist
file.)
Using Vagrant
This skeleton includes a Vagrantfile
based on ubuntu 16.04, and using the
ondrej/php PPA to provide PHP 7.0. Start it up using:
Once built, you can also run composer within the box. For example, the following will install dependencies:
While this will update them:
While running, Vagrant maps your host port 8080 to port 80 on the virtual machine; you can visit the site at http://localhost:8080/
Vagrant and VirtualBox
The vagrant image is based on ubuntu/xenial64. If you are using VirtualBox as a provider, you will need:
- Vagrant 1.8.5 or later
- VirtualBox 5.0.26 or later
For vagrant documentation, please refer to vagrantup.com
Using docker-compose
This skeleton provides a docker-compose.yml
for use with
docker-compose; it
uses the Dockerfile
provided as its base. Build and start the image using:
At this point, you can visit http://localhost:8080 to see the site running.
You can also run composer from the image. The container environment is named
"zf", so you will pass that value to docker-compose run
:
Web server setup
Apache setup
To setup apache, setup a virtual host to point to the public/ directory of the project and you should be ready to go! It should look something like below:
Nginx setup
To setup nginx, open your /path/to/nginx/nginx.conf
and add an
include directive below
into http
block if it does not already exist:
Create a virtual host configuration file for your project under /path/to/nginx/sites-enabled/zfapp.localhost.conf
it should look something like below:
Restart the nginx, now you should be ready to go!
QA Tools
The skeleton does not come with any QA tooling by default, but does ship with configuration for each of:
Additionally, it comes with some basic tests for the shipped
Application\Controller\IndexController
.
If you want to add these QA tools, execute the following:
We provide aliases for each of these tools in the Composer configuration:
All versions of application with dependencies
pacificnm/pacificnm-acl Version dev-master
pacificnm/pacificnm-acl-resource Version dev-master
pacificnm/pacificnm-acl-role Version dev-master
pacificnm/pacificnm-action Version dev-master
pacificnm/pacificnm-admin Version dev-master
pacificnm/pacificnm-auth Version dev-master
pacificnm/pacificnm-config Version dev-master
pacificnm/pacificnm-controller Version dev-master
pacificnm/pacificnm-cron Version dev-master
pacificnm/pacificnm-history Version dev-master
pacificnm/pacificnm-install Version dev-master
pacificnm/pacificnm-log Version dev-master
pacificnm/pacificnm-mapper Version dev-master
pacificnm/pacificnm-menu Version dev-master
pacificnm/pacificnm-menu-item Version dev-master
pacificnm/pacificnm-module Version dev-master
pacificnm/pacificnm-page Version dev-master
pacificnm/pacificnm-update Version dev-master