Download the PHP package ggedde/spry without Composer

Spry

A lightweight PHP API Framework
Great for CRUD applications

@PSR2 and @Symfony Compliant

Documentation

• Installation
• Quick Start
• Configuration
• Components
• Routes
• Database
• Logger
• Response
• Response Codes
• Tests
• Rate Limits
• Lifecycle Hooks & Filters (Middleware)
• Todos

Installation

The best way to install Spry and use it is through the CLI. https://github.com/ggedde/spry-cli

composer global require ggedde/spry-cli

Please reference the Installation Process on the CLI Page.
Then from the command line:

spry new [project_name]
cd [project_name]

An enpoint is automatically created for you

public/index.php

Manual Installation

composer require ggedde/spry

You will need to add the composer autoloader if it has not already been added. Then use the run method and include a path to your config file or include a config object. See configuration

Example:

QuickStart

Create a project through the CLI

spry new [project_name]
cd [project_name]

Folder Structure

- public/
    index.php
- spry/
    - components/
    - logs/
        - api.log
        - php.log
    - config.php
    - init.php

To Start the Spry test server run

spry up

Then open a separate termal and run some tests

spry test

Create a Single FIle Component

spry component MyComponent

Now View and Edit spry/components/MyComponent.php

Update Database Schema from New Component to Database

spry migrate

Run Tests again with new Component

spry test

Thats It!
Happy Coding

Well, I guess you might need more info. Most of all your coding will be in the components files you create and the rest will most likely be in the configuration file. See more details below :)

Configuration

Spry requires a config file or a config object.

When using a config file Spry will pass a pre-initialized $config object to the file. You will just need to set the variables within the object

Example Config File:

Accessing Config Settings

You can access any setting by calling the config() object from Spry

Example:

Extending Config Settings

You can add your own settings and then access them later in your component, provider or plugin

config.php

MyComponent.php

Components

Spry is mainly used through components added in the componentsDir set in the Spry config.

Components are classes within the SpryComponent Namespace.
Components can set their own Routes, Response Codes, DB Schema and Tests by using built in methods. Or you can configure everything through the config.php

These built in Methods are Optional:

Any Methods that resolve a route is called a Controller and gets passed any Parameters from the route.

Basic Example:

Routes

When using single file components you can set the routes in the Components by returning the routes in the getRoutes() method.

Example:

Or within the Config Settings

Route Options

Param Options

Database

Spry's default Database Provider is SpryDB based on Medoo
See SpryDB's full documentation

This allows you to swap out the Provider later on without having to change your project code.

Spry Config Settings

Logger

Spry's default Log Provider is SpryLogger
See SpryLogger's full documentation

This allows you to swap out the Provider later on without having to change your project code.

Spry Configuration

Response

Spry has 2 built in functions for building the response (response and stop).

response

You can use this to build the response data and return it from the Controller.

$responseCode: This is the Response code id from the Component. $responseStatus: This can be either null | info | success | warning | error
If null then the function will auto detect the status based on the value of $data

Example:

stop

This will immediately kill the application and return the response

Example:

* See Response Codes Below to see how this works

ResponseCodes

Single File Component Example:

Config File Example

Notice you will need to add a Group Group Number for the component codes. This is not needed in the Single File Component setup

Component Group Number

The first number is to separate the Components codes by ID
Ex.

1-200   # Success For Component A 
2-200   # Success For Component B 

Multi-Language Support

1 => [
    'success' => [
        'en' => 'Success!',
        'es' => '¡Éxito!'
    ]
]

Format - Info, Success, Redirect or Depricated, Client Error and Server Error

The first number in the code represents the code type.

[group_id]-[1]xx - the 1 represents 'Info' or 'Empty'
[group_id]-[2]xx - the 2 represents 'Success'
[group_id]-[3]xx - the 3 represents 'Redirect' or 'Depricated'
[group_id]-[4]xx - the 4 represents 'Client Error', or 'Unkown'
[group_id]-[5]xx - the 5 represents 'Server Error'

When using Spry::response() you can pass just the last 2 digits as the code and the data parameter.

Ex.

Spry::response($data, 1); 

If $data is an array but empty then the response will automatically Prepend the code with a 1 and return 1-101.
If $data has a value and is not empty then the response will automatically Prepend the code with a 2 and return 1-201.
If $data is an array but not null then the response will automatically Prepend the code with a 4 and return 1-401.
If $data is false or null then the response will automatically Prepend the code with a 5 and return 1-501.

Response Status

In the response there will be a key of status
The possible values for this will only be success, error, or unknown

info, success, and redirect all represent a successfully response and will return success
warning and error represent a failed response and will return error

Tests

Spry comes with its own pre-built testing solution. You can still use other like PHPUnit, but Spry's Tests utilize's Spry's config for rapid testing. When using single file components you can set the routes in the Components by returning the routes in the getTests() method.

Example:

Or within the Config Settings

Test Options

Running Tests with Spry CLI

All Tests

spry test

Specific Test

spry test items_get

More Options

spry test --verbose --repeat 10

RateLimits

Spry's default Rates Limits is SpryRateLimits
See full documentation

This allows you to swap out the Provider later on without having to change your project code.

Add a Global Rate Limit

Adding Limits per route

See full documentation

Lifecycle

Non Lifecycle Hooks & Filters

Hooks

Hooks allow you to run your own code at specific times and life cycles. This is how you can run middleware and other life cycle aware code.

Adding Hooks

Example:

Running Hooks

Example:

Your Controller

Filters

Filters allow you to filter data at specific times and life cycles. A filter typically requires a return value.

Adding Filters

Example:

Running Filters

Example:

Your Controller

Todos

• Add PHPUnit Tests
• Add Types and Interfaces
• Review and optimize Performance
• Review PSR-7 for response
• Drink a Beer!