Download the PHP package spiffy/spiffy-config without Composer

On this page you can find all versions of the php package spiffy/spiffy-config. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package spiffy-config

SpiffyConfig Module

SpiffyConfig is a module designed to speed up configuration.

Installation

Installation of SpiffyConfig uses composer. For composer documentation, please refer to getcomposer.org.

Then add SpiffyConfig to your config/application.config.php

Installation without composer is not officially supported, and requires you to install and autoload the dependencies specified in the composer.json.

Finally, copy config/spiffyconfig.global.php.dist to autoload/spiffyconfig.global.php directory. This will setup the Application module out of the box.

Resolvers

Resolvers pass information to builders so that the builders know what to work on.

Builders

Builders take information from the resolvers and build configurations based on that information.

Supported Annotations

Below is a list of currently supported annotations. This list will be updated as more annotations are supported. In order to use the annotations you must import them first. Do this by putting the following at the top of your code,

This will let you use SpiffyConfig's annotations using @Config in your docblock.

Service

Service annotations are found in the SpiffyConfig\Annotation\Service namespace and handle setting up invokables and factories on various service managers.

Properties:

There are several annotations that extend the service annotations and predefine the key property to save you the extra step. Each of these have a Factory and Invokable annotation available.

Service Annotations:

Route

Route annotations handle setting up routes directly in your controllers. They can be set at the class level or the method level. If set on the class level you must specify the action that the route pertains to. If set directly on the method then the action is set for you.

Currently, the following routes are available:

Example:

Controller

Controllers have an additional RouteParent annotation other than the service annotations listed above. This annotation let's you set the parent for all actions in the current controller.

Options

All options are available in the SpiffyConfig\ModuleOptions class with detailed descriptions.

CLI Tool

A CLI tool is provided to build and clear the cache. Run your public/index.php from a console to see the relevent information.

Automatic Route Names

It's recommended that you specify a name for all routes e.g., @Route\Literal("/", name="home"). Failure to do so will cause an automated route name to be generated based on a canonicalized version of the controller and action name.

For example, if you have a controller registered with the ControllerManager as My\Controller and are a adding a route to the indexAction the auto-generated route name would be my_controller_index.

Zend Developer Tools

A toolbar button is provided if you are using ZendDeveloperTools which lists various SpiffyConfig information and allows you fast access to refreshing the page with the key set.


All versions of spiffy-config with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.3
doctrine/common Version ~2.2
symfony/finder Version ~2.2
zendframework/zend-cache Version ~2.2
zendframework/zend-code Version ~2.2
zendframework/zend-console Version ~2.2
zendframework/zend-log Version ~2.2
zendframework/zend-mvc Version ~2.2
zendframework/zend-serializer Version ~2.2
zendframework/zend-version Version ~2.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package spiffy/spiffy-config contains the following files

Loading the files please wait ....